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 BAF929FAE4E for ; Thu, 18 May 2006 06:01:43 -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 66072-06 for ; Thu, 18 May 2006 06:01:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sand2.gxn.net (sand2.gxn.net [195.147.249.208]) by postgresql.org (Postfix) with ESMTP id 80B149FA218 for ; Thu, 18 May 2006 06:01:28 -0300 (ADT) Received: from [62.232.55.118] (helo=[192.168.0.2]) by sand2.gxn.net with esmtp (Exim 4.50) id 1FgeP4-0004B0-Ci; Thu, 18 May 2006 10:02:42 +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> Content-Type: text/plain Date: Thu, 18 May 2006 10:01:17 +0100 Message-Id: <1147942877.2646.388.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/259 X-Sequence-Number: 21791 On Wed, 2006-05-17 at 22:45 -0700, Jeff Frost wrote: > On Thu, 18 May 2006, Tom Lane wrote: > > > Jeff Frost writes: > >> I seem to get alot of these: > > > >> May 17 21:34:04 discord postgres[20573]: [5-1] WARNING: could not rename file > >> "pg_xlog/archive_status/000000010000000000000001.ready" to > >> May 17 21:34:04 discord postgres[20573]: [5-2] > >> "pg_xlog/archive_status/000000010000000000000001.done": No such file or > >> directory > > > > That seems odd ... > > Further interesting items: > > May 17 22:41:18 discord postgres[23817]: [3-1] LOG: archive command > "/usr/local/pgsql-8.1.3/bin/archive_test.sh "pg_xlog/00000001000000000000000E" > "00000001000000000000000E"" > May 17 22:41:18 discord postgres[23817]: [3-2] failed: return code 256 > And in the window where I started postgres via pg_ctl, I had this: > > cat: pg_xlog/00000001000000000000000E: No such file or directory > cat: pg_xlog/00000001000000000000000E: No such file or directory > > Seems bad. Seems so. Can you post the full test, plus full execution log. [You don't need to "cat" you could just do "ls" instead FWIW] Are you doing *anything* with pg_xlog directory or below? I understand your saying No to that question and pg_xlog has not been moved, its just underneath data directory, which is on normal disk? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com