Morning
I made the mistake of thinking that I could recover to any point in time with a
logical backup plus WAL files, unfortunately that is not the case. I was
rsync'ing wal files to another system, and set the archive timeout to 5 mins,
and the retention to allow for 25 hours worth or so.
On Sep 17, 2013, at 7:22 AM, Echlin, Jamie (KFIA 611)
jamie.ech...@credit-suisse.com wrote:
Unfortunately though if there is heavy load, the wal files will be generated
more regularly than the 5 minute max.
If you wrote the WAL to an external, mounted disk, wouldn't that solve the
issue?
Unfortunately though if there is heavy load, the wal files will be generated
more regularly than the 5 minute max.
If you wrote the WAL to an external, mounted disk, wouldn't that solve the
issue?
What I'm trying to say is that I configured it to keep (60/5) * 24 segments
plus a few
Jamie Echlin wrote:
What I'm trying to say is that I configured it to keep (60/5) * 24 segments
plus a few spare, because
I am switching xlog every 5 mins. But if there is heavy load then they will
be generated more often
than every 5 mins, so that number won't be enough.
You should delete
Thanks for your answer Laurenz.
I was planning to rely on the disk backup (of the base backup) if I wanted to
restore to a version before the last on disk base backup. But your point about
redundancy is good... I think I will keep two base backups, and do a base
backup every day. Over the
Jamie Echlin wrote:
I was planning to rely on the disk backup (of the base backup) if I wanted to
restore to a version
before the last on disk base backup. But your point about redundancy is
good... I think I will keep
two base backups, and do a base backup every day. Over the network this
