From: Simon Riggs <simon@2ndquadrant.com>
To: Kris Kiger <kris@musicrebellion.com>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: archive_command
Date: Fri, 30 Sep 2005 10:13:47 +0100
Message-ID: <1128071627.19345.256.camel@localhost.localdomain> (raw)
In-Reply-To: <433ACE02.3040208@musicrebellion.com>
References: <20031115132118.V74587@holywar.net>
<433AC059.1050300@musicrebellion.com>
<Pine.LNX.4.63.0509280925070.28080@discord.dyndns.org>
<433ACE02.3040208@musicrebellion.com>
On Wed, 2005-09-28 at 12:08 -0500, Kris Kiger wrote:
> My question then is, how do we tell which wal log is X (the one
> currently being written to)?
You don't say why you need to know?
If you really care, you can look at the status files in the
archive_status directory underneath pg_xlog. This is where the archiver
checks to see for notifications of filled WAL files, then clears the
notification afterwards. Only filled WAL filenames are shown.
Don't touch the files or you might interfere with the archiver's
activities.
Best Regards, Simon Riggs
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: simon@2ndquadrant.com, kris@musicrebellion.com, jeff@frostconsultingllc.com
Subject: Re: archive_command
In-Reply-To: <1128071627.19345.256.camel@localhost.localdomain>
References: <20031115132118.V74587@holywar.net> <433AC059.1050300@musicrebellion.com> <Pine.LNX.4.63.0509280925070.28080@discord.dyndns.org> <433ACE02.3040208@musicrebellion.com> <1128071627.19345.256.camel@localhost.localdomain>
* 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