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

Re: does wal archiving block the current client connection?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Frost <jeff(at)frostconsultingllc(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: does wal archiving block the current client connection?
Date: 2006-05-19 16:20:45
Message-ID: 1941.1148055645@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-hackers
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.

What I'd suggest is resuming the test after making sure you've killed
off any old archivers, and seeing if you can make any progress on
reproducing the original problem.  We definitely need a
multiple-archiver interlock, but I think that must be unrelated to your
real problem.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-05-19 16:20:48
Subject: Re: text_position worst case runtime
Previous:From: Tom LaneDate: 2006-05-19 16:17:29
Subject: Re: does wal archiving block the current client connection?

pgsql-admin by date

Next:From: Simon RiggsDate: 2006-05-19 16:25:31
Subject: Re: does wal archiving block the current client connection?
Previous:From: Tom LaneDate: 2006-05-19 16:17:29
Subject: Re: does wal archiving block the current client connection?

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