Re: WAL Archive Log

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Sam Nelson <samn(at)consistentstate(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: WAL Archive Log
Date: 2010-08-28 07:51:23
Message-ID: 1282981883.1800.93.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 2010-08-27 at 09:56 -0600, Sam Nelson wrote:

> Alright, well, we'll probably do something with the archive command,
> then, like either echoing %f to a log file or sending that to syslog
> (and then, after the echo, doing the actual cp or scp or rsync or
> whatever). That way, we should be able to get some form of timestamp
> of when each WAL file is copied to the archive directory (using the
> archive_command), right?
>
>
> Is there any way we could somehow get postgres to log a line for us,
> so that we get that line in the postgres log file? Or are we going to
> have to use a separate file?

Run this every N seconds to get the averaged write rate over the period

SELECT pg_xlogfile_name(pg_current_xlog_location());

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message bitur mail 2010-08-28 16:41:12 two different posgres t for Rails development?
Previous Message Pavel Stehule 2010-08-28 03:25:09 Re: plpgsql question