On Thu, 21 Aug 2008, Glen Parker wrote:
So you advocate archiving the WAL files from a small xlog volume, to a larger
local volume. Why not just make the xlog volume large enough to handle
overruns, since you obviously have the space? Copying each WAL from one
place to another on the local m
On Wed, 20 Aug 2008, Tom Lane wrote:
Greg Smith <[EMAIL PROTECTED]> writes:
You also don't want to be the guy who has to explain why the database is
taking hours to come back up again after it crashed and has 4000 WAL
segments to replay, because archiving failed for a long time and prevented
pr
Greg Smith wrote:
On Wed, 20 Aug 2008, Glen Parker wrote:
The database will continue accumulating WAL segments it can't recycle if
the archiver keeps failing, which can cause the size of the pg_xlog
directory (often mounted into a separate, smaller partition or disk) to
increase dramatically.
Greg Smith <[EMAIL PROTECTED]> writes:
> You also don't want to be the guy who has to explain why the database is
> taking hours to come back up again after it crashed and has 4000 WAL
> segments to replay, because archiving failed for a long time and prevented
> proper checkpoints (ask Robert T
On Wed, 20 Aug 2008, Glen Parker wrote:
Greg Smith wrote:
2) If there is a problem with the network drive, the slow/blocked network
write is not happening where the database is waiting for it.
This is not really a consideration, is it? I was under the impression that
no other database activ
Greg Smith wrote:
2) If there is a problem with the network drive, the slow/blocked
network write is not happening where the database is waiting for it.
This is not really a consideration, is it? I was under the impression
that no other database activity blocks waiting for the archiver. That
On Tue, 19 Aug 2008, Rob Adams wrote:
Is it best to give the 'postgres' user network access & archive the WAL files
directly to the network drive? Or archive the WAL files to a local folder and
then use a scheduled task to move them to the network drive?
I normally write first to a local driv
Rob Adams wrote:
I'm setting up WAL archiving on a Windows machine & need to copy the WAL
files to a network drive.
Is it best to give the 'postgres' user network access & archive the WAL
files directly to the network drive? Or archive the WAL files to a local
folder and then use a scheduled
