Jeff Janes wrote
> That's not really true. There are no per-row WAL records. There is still
> a per-transaction WAL record, the commit record. If you only care about
> the
> timing of the WAL and not the volume, changing to unlogged will not make a
> difference. (These commit-only records are automatically dealt with
> asynchronously, even if synchronous-commit is on.)
>
> Cheers,
>
> Jeff
Hi,
just to understand this answer:
Is it *NOT* possible to create an unlogged table where inserts or updates
will *NOT* modify the WAL files?
Regards, hall
--
View this message in context: http://postgresql.nabble.com/Will-modifications-to-unlogged-tables-also-be-flused-to-disk-tp5792158p5829600.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.