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 303729FA19B for ; Wed, 17 May 2006 01:36:28 -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 13494-06 for ; Wed, 17 May 2006 01:36:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 296FF9F9C9E for ; Wed, 17 May 2006 01:36:21 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4H4a9AB015700; Wed, 17 May 2006 00:36:09 -0400 (EDT) To: Jeff Frost cc: Simon Riggs , pgsql-admin@postgresql.org Subject: Re: does wal archiving block the current client connection? In-reply-to: References: <1147728181.5074.73.camel@localhost.localdomain> <1147733193.5074.87.camel@localhost.localdomain> <1147781287.2646.32.camel@localhost.localdomain> Comments: In-reply-to Jeff Frost message dated "Tue, 16 May 2006 11:22:27 -0700" Date: Wed, 17 May 2006 00:36:09 -0400 Message-ID: <15699.1147840569@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/230 X-Sequence-Number: 21762 Jeff Frost 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