Yes, it does indeed interleave and it seems to archive the backlog just
before the files are about to be deleted. That explains it.
Thanks for your help,
Neil
2013/1/31 Jeff Janes
> On Thu, Jan 31, 2013 at 12:50 AM, Neil Worden
> wrote:
> >
> > The situation is as fo
-backup + an endless stream of wal files" backup-strategy if
the files in my wal archive get overwritten and i don´t "save" them to
another place before that happens.
2013/1/31 Adrian Klaver
> On 01/31/2013 01:48 AM, Neil Worden wrote:
>
>>
>> Btw, ps shows:
process last was 0001008E0058
postgres 11504 0.0 0.0 20816 1412 ?Ss Jan29 0:54 postgres:
stats collector process
Am i missing something ?
Thanks, Neil
2013/1/31 Neil Worden
>
> Btw, ps shows:
>
> postgres@darkblue:/data/pgdata/pg_xlog$ ps aux | grep pos
Any ideas ?
Thanks, Neil.
2013/1/31 Neil Worden
> >>> If your command does overwrite, then the server currently emitting the
> >>> 8D files will become unrecoverable once those files start getting
> >>> overwritten. If it refuses to overwrite, but returns
>>> If your command does overwrite, then the server currently emitting the
>>> 8D files will become unrecoverable once those files start getting
>>> overwritten. If it refuses to overwrite, but returns a zero status,
>>> then the server currently emitting 6D would become unrecoverable once
>>> it
Hi all,
i am not sure whether i have fully understood the implications of
archiving wal-files and i have a few questions.
We currently keep a rather long backlog of wal-files, since we have a few
hot-standbys over slow and unreliable lines that might fall back. So this
is an extract from my curr
