From: masterchief <esimon@theiqgroup.com>
To: pgsql-admin@postgresql.org
Subject: Warnings in Standby Logs
Date: Sat, 17 Mar 2012 21:29:04 -0700 (PDT)
Message-ID: <1332044944364-5574652.post@n5.nabble.com> (raw)
Hi,
I'm on 9.1.2 and occasionally get what are probably harmless warning
messages in my logs, but because I have the responbility of ensuring we
haven't lost a bit of data between our master and standby, I feel I should
know exactly what they mean. I occasionally see "invalid record length" and
"record with zero length" in my logs, and they almost only occur during
reboots (the "consistent recovery state reached" message gives me the
warm-fuzzy, but then when they're followed by either of those two, it leaves
me wondering). For example, I had to reboot my hot standby twice yesterday:
2012-03-16 10:23:28 CDT LOG: received smart shutdown request
2012-03-16 10:23:28 CDT FATAL: terminating walreceiver process due to
administrator command
2012-03-16 10:27:33 CDT LOG: database system was interrupted while in
recovery at log time 2012-03-16 10:14:15 CDT
2012-03-16 10:27:33 CDT HINT: If this has occurred more than once some data
might be corrupted and you might need to choose an earlier recovery target.
2012-03-16 10:27:33 CDT LOG: entering standby mode
2012-03-16 10:27:34 CDT LOG: redo starts at 9/B98D6968
2012-03-16 10:27:34 CDT LOG: consistent recovery state reached at
9/B9F171B0
2012-03-16 10:27:34 CDT LOG: database system is ready to accept read only
connections
2012-03-16 10:27:34 CDT LOG: invalid record length at 9/B9F85E78
2012-03-16 10:27:34 CDT LOG: streaming replication successfully connected
to primary
2012-03-16 10:28:07 CDT LOG: received smart shutdown request
2012-03-16 10:28:07 CDT FATAL: terminating walreceiver process due to
administrator command
2012-03-16 10:28:07 CDT LOG: shutting down
2012-03-16 10:47:00 CDT LOG: database system was interrupted while in
recovery at log time 2012-03-16 10:14:15 CDT
2012-03-16 10:47:00 CDT HINT: If this has occurred more than once some data
might be corrupted and you might need to choose an earlier recovery target.
2012-03-16 10:47:00 CDT LOG: entering standby mode
2012-03-16 10:47:01 CDT LOG: redo starts at 9/B98D6968
2012-03-16 10:47:02 CDT LOG: consistent recovery state reached at
9/BA2D3490
2012-03-16 10:47:02 CDT LOG: database system is ready to accept read only
connections
2012-03-16 10:47:02 CDT LOG: invalid record length at 9/BA2D3490
2012-03-16 10:47:02 CDT LOG: streaming replication successfully connected
to primary
Is this something I should be concerned about (and even if not, where can I
read about what these mean in detail)?
Also, is there maybe a more elegant shutdown I can use in my Linux shutdown
scripts?
P.S. I have searched the forums and the docs several times, so I apologize
if I missed the answer/tutorial on this somewhere.
Thanks,
Eric Simon
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Warnings-in-Standby-Logs-tp5574652p5574652.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: esimon@theiqgroup.com
Subject: Re: Warnings in Standby Logs
In-Reply-To: <1332044944364-5574652.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox