Feature Suggestion: Make synchronous_commit a table level property

Hi hackers,


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.

What are your thoughts on this, and potentially adding such support in
future postgres versions?


Thanks,
AK