pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: does wal archiving block the current client connection?
Date: Wed, 17 May 2006 23:24:45 -0400
Message-ID: <7583.1147922685@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0605170909020.3380@glacier.frostconsultingllc.com>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
	<1147728181.5074.73.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org>
	<1147733193.5074.87.camel@localhost.localdomain>
	<Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org>
	<1147781287.2646.32.camel@localhost.localdomain>
	<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>

Jeff Frost <jeff@frostconsultingllc.com> writes:
> Was the 3,000 transactions per minute helpful?  What other evidence should I 
> be looking for?

Did you try generating a test case using a long sleep() as a replacement
for the archive_command script?  If there is a PG bug here it shouldn't
be that hard to expose it in a simple test case.  I'm up to my armpits
in other stuff and don't have time to try it myself...

			regards, tom lane



view thread (55+ messages)  latest in thread

Message-ID: <7583.1147922685@sss.pgh.pa.us>
Permalink:  ../7583.1147922685@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/7583.1147922685@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jeff@frostconsultingllc.com, simon@2ndquadrant.com
  Subject: Re: does wal archiving block the current client connection?
  In-Reply-To: <7583.1147922685@sss.pgh.pa.us>
  References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <1147728181.5074.73.camel@localhost.localdomain> <Pine.LNX.4.64.0605151424500.9581@discord.dyndns.org> <1147733193.5074.87.camel@localhost.localdomain> <Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org> <1147781287.2646.32.camel@localhost.localdomain> <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>

* 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