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 C7B6F9FA2C8 for ; Mon, 15 May 2006 18:23:22 -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 72939-08 for ; Mon, 15 May 2006 18:23:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by postgresql.org (Postfix) with ESMTP id CCAEE9FA15C for ; Mon, 15 May 2006 18:23:14 -0300 (ADT) Received: from [195.112.19.37] (helo=[192.168.0.7]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis), id 0ML2ov-1FfkWy0hpK-0003G9; Mon, 15 May 2006 23:23:08 +0200 Subject: Re: does wal archiving block the current client connection? From: Simon Riggs To: Jeff Frost Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Date: Mon, 15 May 2006 22:23:00 +0100 Message-Id: <1147728181.5074.73.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:726643fe08f41a451f0fe7fa43bce239 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/201 X-Sequence-Number: 21733 On Mon, 2006-05-15 at 09:28 -0700, Jeff Frost wrote: > 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 What kind of problems? > , it seems that the current client connection gets blocked and this > eventually builds up to a "sorry, too many clients already" error. This sounds like the archiver keeps waking up and trying the command, but it fails, yet that request is causing a resource leak on the NAS. Eventually, archiver retrying the command eventually fails. Or am I misunderstanding your issues? > I'm > wondering if this is expected behavior with the archive command and if I > should build in some more smarts to my archive script. Maybe I should fork > and waitpid such that I can use a manual timeout shorter than whatever the > CIFS timeout is so that I can return an error in a reasonable amount of time? The archiver is designed around the thought that *attempting* to archive is a task that it can do indefinitely without a problem; its up to you to spot that the link is down. We can put something in to make the retry period elongate, but you'd need to put a reasonable case for how that would increase robustness. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com