X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id AAE539FA372 for ; Fri, 19 May 2006 09:26:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 52820-03 for ; Fri, 19 May 2006 09:26:44 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sand4.gxn.net (sand4.gxn.net [195.147.249.239]) by postgresql.org (Postfix) with ESMTP id 8A01A9F9AFD for ; Fri, 19 May 2006 09:26:40 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand4.gxn.net with esmtp (Exim 4.50) id 1Fh42V-0006jn-NK; Fri, 19 May 2006 13:25:07 +0100 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Jeff Frost Cc: Tom Lane , pgsql-admin@postgresql.org In-Reply-To: References: <1147728181.5074.73.camel@localhost.localdomain> <1147733193.5074.87.camel@localhost.localdomain> <1147781287.2646.32.camel@localhost.localdomain> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <7583.1147922685@sss.pgh.pa.us> <8269.1147927511@sss.pgh.pa.us> <1147942877.2646.388.camel@localhost.localdomain> Content-Type: text/plain Date: Fri, 19 May 2006 13:26:33 +0100 Message-Id: <1148041593.2646.592.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/271 X-Sequence-Number: 21803 On Thu, 2006-05-18 at 10:08 -0700, Jeff Frost wrote: > May 18 08:00:18 discord postgres[20228]: [129-1] LOG: archived transaction log file "00000001000000000000007F" > May 18 08:00:41 discord postgres[20573]: [254-1] LOG: archived transaction log file "00000001000000000000007F" > May 18 08:00:41 discord postgres[20573]: [255-1] WARNING: could not rename file "pg_xlog/archive_status/00000001000000000000007F.ready" to > May 18 08:00:41 discord postgres[20573]: [255-2] "pg_xlog/archive_status/00000001000000000000007F.done": No such file or directory I'm not clear how you can have two processes both issuing this message, since it is only the archiver process that ever says this. Do you have two archivers running on this system? pid = 20229 and pid = 20573 Presumably pg_xlog/archive_status/00000001000000000000007F.done already exists? Are there two postmasters running (at all)? Is there somehow an archiver process running from a previously shutdown postmaster (somehow)? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com