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 b
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
Excerpts from Sam Nelson's message of jue ago 26 19:24:00 -0400 2010:
> Is there a way to get postgres to write a line to the log file when it
> creates a WAL file? We wrote a script that tries to grab the times between
> WAL file creation and ingestion without stopping to make absolutely sure
> t
Is there a way to get postgres to write a line to the log file when it
creates a WAL file? We wrote a script that tries to grab the times between
WAL file creation and ingestion without stopping to make absolutely sure
that postgres actually logs the WAL file creation, and so we're kinda stuck
sta
