From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | German Becker <german(dot)becker(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: WAL files not following sequence |
Date: | 2013-05-23 08:33:25 |
Message-ID: | CA+HiwqGgVzxJD9SQBng1fLEOt-77Fd3bDkNw3WC7ZGFd9zrpwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
I got response from pgsql-hackers that it is normal. In fact, the
newer segments that you see are pre-allocated ones (none of those
contain any valid WAL data as of now). And WAL data is currently being
written to an earlier segment like 000000010000000E00000080 (which
seems to be the latest in your "ls -lrt" output).
By the way, what are the values of following configuration parameters
for your cluster?
checkpoint_segments=?
checkpoint_timeout=?
archive_mode=?
archive_command=?
--
Amit Langote
From | Date | Subject | |
---|---|---|---|
Next Message | Maletin von Oertzen | 2013-05-23 13:02:10 | Re: HOT Standby - slave does not appear to be removing wal files |
Previous Message | Amit Langote | 2013-05-23 08:03:35 | Re: WAL files not following sequence |