Store mostly static data for engineering

Please bear with me, I'm a mechanical engineer by training, We are looking to migrate away from tables in Excel to something else. On of the choices is a real database of somesort, and I'll be trying to push for an opensource option.

We store engineering data in tables in excel. Things like weight, Partnumber, physical characteristics, electrical characteristics, clearances, etc. Some of these we create views of via powerquery for specific use cases.

What I'd like to do is move this all to a database. But I don't see a good say the snapshot and rev control a specific state of a database (schema?) including the records. We'd like to serve that snapshot version, while making changes as needed to the "beta" version, before snapshotting again. This is would be a few to several manual updates per day, followed by aeeks to months of no changes.

My questions:

1. Is this a normal thing to want to do with a database?
2. Can postgresql do it somehow and what should i be looking for in the docs?