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 DB1EE9FA1F1 for ; Mon, 15 May 2006 15:23:17 -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 22400-02 for ; Mon, 15 May 2006 15:23:13 -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 5115B9FA15C for ; Mon, 15 May 2006 15:23:13 -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 k4FIN9LL010693; Mon, 15 May 2006 14:23:09 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: Comments: In-reply-to Jeff Frost message dated "Mon, 15 May 2006 09:28:25 -0700" Date: Mon, 15 May 2006 14:23:09 -0400 Message-ID: <10692.1147717389@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/191 X-Sequence-Number: 21723 Jeff Frost writes: > I've run into a problem with a PITR setup at a client. The problem is that > whenever the CIFS NAS device that we're mounting at /mnt/pgbackup has > problems, it seems that the current client connection gets blocked and this > eventually builds up to a "sorry, too many clients already" error. I'm > wondering if this is expected behavior with the archive command 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. What PG version is this exactly? Are you sure that the only connection of the NAS device to PG operations is through the archive script, ie, you don't have any part of the normal PG data directory mounted on it? regards, tom lane