From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [ADMIN] does wal archiving block the current client connection?
Date: Fri, 19 May 2006 12:03:17 -0400
Message-ID: <727.1148054597@sss.pgh.pa.us> (raw)
In-Reply-To: <1148054357.2646.662.camel@localhost.localdomain>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org>
<Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org>
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.
regards, tom lane
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, simon@2ndquadrant.com, jeff@frostconsultingllc.com, pgsql-hackers@postgreSQL.org
Subject: Re: [ADMIN] does wal archiving block the current client connection?
In-Reply-To: <727.1148054597@sss.pgh.pa.us>
References: <Pine.LNX.4.64.0605150914360.9581@discord.dyndns.org> <Pine.LNX.4.64.0605151554000.9581@discord.dyndns.org> <727.1148054597@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