pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Mon, 15 May 2006 22:23:00 +0100
Message-ID: <1147728181.5074.73.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>

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




view thread (55+ messages)  latest in thread

Message-ID: <1147728181.5074.73.camel@localhost.localdomain>
Permalink:  ../1147728181.5074.73.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1147728181.5074.73.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, jeff@frostconsultingllc.com
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <1147728181.5074.73.camel@localhost.localdomain>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <1147728181.5074.73.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox