On Mon, Feb 11, 2013 at 5:46 PM, Pavan Deolasee <[email protected]> wrote: > On Fri, Feb 8, 2013 at 10:25 PM, Fujii Masao <[email protected]> wrote: > .> >> BTW, the cause of the problem is that the following sequences happens. >> >> 1. archive_timeout switches WAL file because checkpoint WAL record has >> has been written since last switch > > Thank you for explaining that. I also noticed that the WAL file switch > happens after archive_timeout seconds irrespective of whether > archive_mode is turned ON or not. This happens because we don't check > if XLogArchivingActive() in CheckArchiveTimeout() function. It looks > wrong to me.
+1 to fix this. I've not heard the use case where archive_timeout needs to be used even in not archive mode... Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
