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

Re: archive_command

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Kris Kiger <kris(at)musicrebellion(dot)com>
Cc: Jeff Frost <jeff(at)frostconsultingllc(dot)com>,pgsql-admin(at)postgresql(dot)org
Subject: Re: archive_command
Date: 2005-09-30 09:13:47
Message-ID: 1128071627.19345.256.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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

Best Regards, Simon Riggs

In response to


pgsql-admin by date

Next:From: RytisDate: 2005-09-30 16:14:44
Subject: data files corruption after server crash
Previous:From: Gourish SingbalDate: 2005-09-30 06:06:41
Subject: Re: data corruption

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