On 11/17/2013 4:46 PM, Edson Richter wrote:
There is no reason to wait for fsync in slow disks to guarantee consistency... If database server crashes, then it just need to "redo" log transactions from fast disk into slower data storage and database server is ready to go (I think this is Sybase/MS SQL strategy for years).
you need to fsync that slower disk before you can purge the older WAL or redo log, whatever, from your fast storage. this fsync can, of course, be quite a ways behind the current commit status.
-- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
