Hi, On Fri, Apr 24, 2009 at 3:20 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > It's not safe to write WAL after the checkpoint, as RequestXLogSwitch() > does. After restart, the system will start inserting WAL from the checkpoint > redo point, which is just before the XLOG_SWITCH record, and will overwrite > it.
Since, in this case, the WAL file including XLOG_SWITCH exists in archive, I don't think that it's unsafe, i.e. XLOG_SWITCH would be treated as the last applied record and not be overwritten. WAL records would start to be inserted from the subsequent file (with new timeline). This is useful for warm-standby, but I'm afraid that this may delay Shared Disk Failover which doesn't need to wait until all the WAL files are archived at shutdown. Is there any solution to this problem? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
