Re: [ADMIN] does wal archiving block the current client connection? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [ADMIN] does wal archiving block the current client connection?
Date
Msg-id 1148056053.2646.672.camel@localhost.localdomain
Whole thread Raw
In response to Re: [ADMIN] does wal archiving block the current client connection?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [ADMIN] does wal archiving block the current client  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Fri, 2006-05-19 at 12:03 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > OK, I'm on it.
> 
> What solution have you got in mind?  I was thinking about an fcntl lock
> to ensure only one archiver is active in a given data directory.  That
> would fix the problem without affecting anything outside the archiver.
> Not sure what's the most portable way to do it though.

I was trying to think of a better way than using an archiver.pid file in
pg_xlog/archive_status...

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: [OT] MySQL is bad, but THIS bad?
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [OT] MySQL is bad, but THIS bad?