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 00:36:09 -0400
Message-ID: <15699.1147840569@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.64.0605161119330.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>

Jeff Frost <jeff@frostconsultingllc.com> writes:
> On Tue, 16 May 2006, Simon Riggs wrote:
>> Whatever happened between 02:08 and 02:14 seems important.

> I have the logs and after reviewing /var/log/messages for that time period, 
> there is no other activity besides postgres.

I have a lurking feeling that the still-hypothetical connection between
archiver and foreground operations might come into operation at pg_clog
page boundaries (which require emitting XLOG events) --- that is, every
32K transactions something special happens.  The time delay between
archiver wedging and foreground wedging would then correspond to how
long it took the XID counter to reach the next 32K multiple.  (Jeff,
what transaction rate do you see on that server --- is that a plausible
delay for some thousands of transactions to pass?)

This is just a guess, but if you check the archives for Chris K-L's
out-of-disk-space server meltdown a year or three ago, you'll see
something similar.

			regards, tom lane



view thread (55+ messages)  latest in thread

Message-ID: <15699.1147840569@sss.pgh.pa.us>
Permalink:  ../15699.1147840569@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15699.1147840569@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: <15699.1147840569@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>

* 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