Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XB0rq-00008m-1s for pgsql-admin@arkaria.postgresql.org; Sat, 26 Jul 2014 12:14:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XB0ro-000715-SW for pgsql-admin@arkaria.postgresql.org; Sat, 26 Jul 2014 12:14:24 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XB0rn-00070y-Nt for pgsql-admin@postgresql.org; Sat, 26 Jul 2014 12:14:23 +0000 Received: from mout.kundenserver.de ([212.227.17.24]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XB0rj-0005GF-TM for pgsql-admin@postgresql.org; Sat, 26 Jul 2014 12:14:22 +0000 Received: from ayaki.localdomain (106-69-201-238.dyn.iinet.net.au [106.69.201.238]) by mrelayeu.kundenserver.de (node=mreue105) with ESMTP (Nemesis) id 0LfSUj-1Wi0dy1VPt-00p2UN; Sat, 26 Jul 2014 14:14:16 +0200 Message-ID: <53D39B93.1030207@2ndquadrant.com> Date: Sat, 26 Jul 2014 20:14:11 +0800 From: Craig Ringer Organization: 2nd Quadrant User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: John Scalia , "pgsql-admin@postgresql.org" Subject: Re: WAL segment management on a standby References: <53C015AA.5070908@gmail.com> <53C33DE8.7000902@2ndquadrant.com> <53C3E1AC.60704@gmail.com> In-Reply-To: <53C3E1AC.60704@gmail.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:WSEFUsuJhi8RAQdMownzLbfJS/cKs/+hsMrLQkt6Lxn 9OAhqa3kVQ9oEYUcNMk/d4m0KEp85h1Ijj9DY1jaDVy4s96c+B ahGvlZlsQJHkAxJa90YohOT+bC+V7gzACI1OGZcTp+B5AV00I8 8adGz+BKzZPofCyNmBFLBNcsu/HHAv3JzY3Tz0GnRou1COA2bX ePliYWO/xulYwdZ2aiiEwKlvmSqQRXxMGfKKX9v6ZSn91l59yu lSGE6hasUnPbfPzpo4qJDlYsdjEfKeJYqkOLPj54o7fJzuw7Ys P/Jjw8roTyxeM6vq3l7/dk8X3Fnd02v4KDc00mDb0kRj/5pOyD 8xljuQzG0BIasz4a6O0SHb+OTdFFT07zLP780Go85 X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 07/14/2014 09:57 PM, John Scalia wrote: > > First, it whined about no history.0000004 file, which as the last WAL > segment is 0000000030000000E00000004E, I'm guessing the standby thought > the timeline might have been changed, but it was not. Then, it > complained about no history.00000003 file in the archive area. This file > had already been copied up into pg_xlog and deleted from the archive. No immediate answer for you there. > Finally, the last complaint was that it couldn't find > 0000000030000000E00000004F in the archive. It appears that under > streaming a standby server will write concurrently with the primary any > WAL segment the primary is still generating. I say this as that missing > WAL segment ("...4F") was already in the pg_xlog directory, but it > hadn't yet made it into the archive area. Eventually, 10 minutes later, > 4F did appear in the archive. Is my interpretation here correct, that a > standby will concurrently write a WAL segment in streaming replication > mode? The xlog files get written to in pg_xlog until they're rotated. When rotated, they get archived; when the archive command completes, they become accessible to standby servers. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin