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 0C58D9FA2C8 for ; Mon, 15 May 2006 15:33:59 -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 21866-10 for ; Mon, 15 May 2006 15:33:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id C5EFD9FA15C for ; Mon, 15 May 2006 15:33:48 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4FIXhZH010785; Mon, 15 May 2006 14:33:43 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: <10692.1147717389@sss.pgh.pa.us> Comments: In-reply-to Jeff Frost message dated "Mon, 15 May 2006 11:31:13 -0700" Date: Mon, 15 May 2006 14:33:43 -0400 Message-ID: <10784.1147718023@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/193 X-Sequence-Number: 21725 Jeff Frost writes: > On Mon, 15 May 2006, Tom Lane wrote: >> No, I can't see what the connection should be there. It's supposed to >> be designed so that the archive command can take its sweet old time and >> nothing happens except that a backlog of WAL files builds up in pg_xlog. > That's what I thought, but that doesn't seem to be what I'm observing. Of > course the NAS device only gets wedged about once every month or two, so it's > difficult to reproduce. If it's really a PG bug, it should be trivial to reproduce: put a long sleep in the archive-command script. regards, tom lane