pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Fri, 19 May 2006 17:25:31 +0100
Message-ID: <1148055931.2646.669.camel@localhost.localdomain> (raw)
In-Reply-To: <1941.1148055645@sss.pgh.pa.us>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
	<Pine.LNX.4.64.0605161119330.3380@glacier.frostconsultingllc.com>
	<15699.1147840569@sss.pgh.pa.us>
	<1147858398.2646.150.camel@localhost.localdomain>
	<19436.1147874478@sss.pgh.pa.us>
	<Pine.LNX.4.64.0605170909020.3380@glacier.frostconsultingllc.com>
	<7583.1147922685@sss.pgh.pa.us>
	<Pine.LNX.4.64.0605172134370.7012@discord.home.frostconsultingllc.com>
	<8269.1147927511@sss.pgh.pa.us>
	<1879.1148055449@sss.pgh.pa.us>
	<1941.1148055645@sss.pgh.pa.us>

On Fri, 2006-05-19 at 12:20 -0400, Tom Lane wrote:
> I wrote:
> > Well, the fact that there's only one archiver *now* doesn't mean there
> > wasn't more than one when the problem happened.  The orphaned archiver
> > would eventually quit.
> 
> But, actually, nevermind: we have explained the failures you were seeing
> in the test setup, but a multiple-active-archiver situation still
> doesn't explain the original situation of incoming connections getting
> blocked.

Agreed.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com




view thread (55+ messages)  latest in thread

Message-ID: <1148055931.2646.669.camel@localhost.localdomain>
Permalink:  ../1148055931.2646.669.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1148055931.2646.669.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, tgl@sss.pgh.pa.us, jeff@frostconsultingllc.com, pgsql-hackers@postgresql.org
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <1148055931.2646.669.camel@localhost.localdomain>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <Pine.LNX.4.64.0605161119330.3380@glacier.frostconsultingllc.com> <15699.1147840569@sss.pgh.pa.us> <1147858398.2646.150.camel@localhost.localdomain> <19436.1147874478@sss.pgh.pa.us> <Pine.LNX.4.64.0605170909020.3380@glacier.frostconsultingllc.com> <7583.1147922685@sss.pgh.pa.us> <Pine.LNX.4.64.0605172134370.7012@discord.home.frostconsultingllc.com> <8269.1147927511@sss.pgh.pa.us> <1879.1148055449@sss.pgh.pa.us> <1941.1148055645@sss.pgh.pa.us> <1148055931.2646.669.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