David G Johnston wrote
> Well, that is half right anyway. UNLOGGED tables obey checkpoints just
> like any other table. The missing feature is an option to leaved restored
> the last checkpoint. Instead, not knowing whether there were changes
> since the last checkpoint, the system truncated the
That will be a very useful feature. I don'
t care if i loss 1-2 hours of data. I know we could have some cron jobs to
dump the table periodically but the table could be big, so this operation
could be expensive. Also i have to detect when postgres crush, i have no
idea how i can detect if postgr
"In the event of a normal shutdown, we can flush all the writes to disk
so we know all the data has been written, so there is no need to truncate."
Isn't possible to periodically flush data to disk and in case of crush
postgres to load only the data that existed at last flush? The periodic
flush
