sergeyprokhoren

The PostgreSQL uuidv7() developers are leaning toward a different approach to solving timestamp leaks, similar to FHSS (https://en.wikipedia.org/wiki/Frequency-hopping_spread_spect...). This is currently possible manually using the parameter "shift" (https://postgrespro.ru/docs/postgresql/18/functions-uuid), but could be automated in the near future

This is a fairly common problem. Data is often transferred between information systems in denormalized form (tables with hundreds of columns - attributes). In the data warehouse, they are normalized (data duplication in tables is excluded by using references to reference tables) to make it easier to perform complex analytical queries to the data. Usually, they are normalized to 3NF and very rarely to 6NF, since there is still no convenient tool for 6NF (see my DSL: https://medium.com/@sergeyprokhorenko777/dsl-for-bitemporal-... ). And then the data is again denormalized in data marts to generate reports for external users. All these cycles of normalization - denormalization - normalization - denormalization are very expensive for IT departments. Therefore, I had an idea to transfer data between information systems directly in normalized form, so that nothing else would have to be normalized. The prototypes were the Anchor Modeling and (to a much lesser extent) Data Vault methodologies.