## Anas-ur-Rasheed Khan (annich...@gmail.com): > We have a use case where some tables are derived, i.e., can be > reconstructed entirely from 'source' tables (similar to views, but more > complex mathematical transformations are applied). Data integrity and > durability are important for 'source' tables, but not so much for derived > tables. In the event of a crash, it is important that we can recover data > from volatile memory for 'source' tables.
Did you consider unlogged tables? https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-UNLOGGED The documentation says "considerably faster than ordinary tables" but "automatically truncated after a crash" which might fit your requirements. "Synchronous Commit" should be understood as transaction property and does not really work on a table level. Regards, Christoph -- Spare Space.
