Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 355C11782AF6 for ; Mon, 2 Apr 2012 13:45:01 -0300 (ADT) Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SEkNI-0003U8-Mn for pgsql-admin@postgresql.org; Mon, 02 Apr 2012 16:45:01 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SEkN5-0006gn-Eb for pgsql-admin@postgresql.org; Mon, 02 Apr 2012 09:44:47 -0700 Date: Mon, 2 Apr 2012 09:44:47 -0700 (PDT) From: masterchief To: pgsql-admin@postgresql.org Message-ID: <1333385087445-5613002.post@n5.nabble.com> In-Reply-To: References: <003501cd0e91$0eee7dd0$2ccb7970$@theiqgroup.com> Subject: Re: Warnings in Standby Logs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.8 (/) X-Archive-Number: 201204/4 X-Sequence-Number: 39340 I see. Is there a more elegant way that I could shut down my standby server so that it would be in a more clean state? For example, when I first built the standby and began replication, I didn't get either of those record length messages. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Warnings-in-Standby-Logs-tp5607135p5613002.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.