Skip site navigation (1) Skip section navigation (2)

Re: does wal archiving block the current client connection?

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: does wal archiving block the current client connection?
Date: 2006-05-18 14:54:51
Message-ID: Pine.LNX.4.64.0605180750580.5387@discord.home.frostconsultingllc.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
On Thu, 18 May 2006, Simon Riggs wrote:

> Seems so.
>
> Can you post the full test, plus full execution log.
>
> [You don't need to "cat" you could just do "ls" instead FWIW]
>
> Are you doing *anything* with pg_xlog directory or below? I understand
> your saying No to that question and pg_xlog has not been moved, its just
> underneath data directory, which is on normal disk?

I did a fresh compile of 8.1.3 with --prefix=/usr/local/pgsql-8.1.3.  On this 
particular system, this is actually located on / which is /dev/md1 (a mirror).
I'll try and start a brand new version of the test so I can capture the 
logging to syslog for you guys as well as the stdout on the pg_ctl console.

More later.

Unfortunately, I'm not really sure this is related to the problems we saw 
before.  (i.e. the system doesn't get unusually slow or anything, nor do the 
connections seems to block)

-- 
Jeff Frost, Owner 	<jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2006-05-18 15:31:22
Subject: Re: Google and the Beta Freeze
Previous:From: Tom LaneDate: 2006-05-18 14:39:24
Subject: Re: Google and the Beta Freeze

pgsql-admin by date

Next:From: Warren LittleDate: 2006-05-18 16:05:55
Subject: query optimization - mysql vs postgresql
Previous:From: Tom LaneDate: 2006-05-18 13:45:54
Subject: Re: does wal archiving block the current client connection?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group