Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TOtzK-0001xA-NM for pgsql-admin@postgresql.org; Thu, 18 Oct 2012 17:34:30 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TOtzF-0006QS-Se for pgsql-admin@postgresql.org; Thu, 18 Oct 2012 17:34:29 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TOtzF-0000DG-KD for pgsql-admin@postgresql.org; Thu, 18 Oct 2012 10:34:25 -0700 Date: Thu, 18 Oct 2012 10:34:25 -0700 (PDT) From: Parkirat Bagga To: pgsql-admin@postgresql.org Message-ID: <1350581665615-5728878.post@n5.nabble.com> In-Reply-To: References: <1350506189966-5728705.post@n5.nabble.com> Subject: Re: WAL corruption while replication MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.0 (/) X-Archive-Number: 201210/78 X-Sequence-Number: 40194 Thanks Albe for the clarification. Regards, Parkirat Singh Bagga. -- View this message in context: http://postgresql.1045698.n5.nabble.com/WAL-corruption-while-replication-tp5728705p5728878.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.