Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 2ED3814D375 for ; Sun, 18 Mar 2012 01:29:21 -0300 (ADT) Received: from sam.nabble.com ([216.139.236.26]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S97k6-0006iK-SO for pgsql-admin@postgresql.org; Sun, 18 Mar 2012 04:29:20 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1S97js-00029d-By for pgsql-admin@postgresql.org; Sat, 17 Mar 2012 21:29:04 -0700 Date: Sat, 17 Mar 2012 21:29:04 -0700 (PDT) From: masterchief To: pgsql-admin@postgresql.org Message-ID: <1332044944364-5574652.post@n5.nabble.com> Subject: Warnings in Standby Logs MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24562_9312382.1332044944366" X-Pg-Spam-Score: -0.8 (/) X-Archive-Number: 201203/99 X-Sequence-Number: 39287 ------=_Part_24562_9312382.1332044944366 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. ------=_Part_24562_9312382.1332044944366 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 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: Warnings in Standby Logs
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
------=_Part_24562_9312382.1332044944366--