From: steve@outtalimits.com.au
To: windsurferdrew-pg@yahoo.com
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL files during a backup
Date: Thu, 28 Aug 2008 06:36:24 +1000
Message-ID: <7d15abe81b5970cf29b154bb23ac3ed6@127.0.0.1> (raw)
In-Reply-To: <749976.10730.qm@web36902.mail.mud.yahoo.com>
References: <749976.10730.qm@web36902.mail.mud.yahoo.com>
00000001000000000000223387 would usually be the next WAL to be written.
How often are you WALs written out?
On Wed, 27 Aug 2008 07:07:17 -0700 (PDT), windsurferdrew-pg@yahoo.com
wrote:
> I have a question regarding the WAL files that are moved during a backup
to
> the "archive directory".
>
> I have setup the postgresql.conf file to have the following archive
> command:
>
> archive_command = 'cp -i %p /var/lib/pgsql/backups/%f </dev/null'
>
> Environment:
> PG Version 8.1.4
> OS: Linux 2.6.18-8.el5
>
> After I have run the pg_hotbackup script, the backups directory contains
> only 2 files:
> 1. The gzipped tar file pg_hotbackup_<timestamp>.tar.gz, and
> 2. a WAL file ".backup" file, (for example
> 00000001000000000000223387.0089ED8C.backup)
>
> The actual WAL file did not get copied to the backups directory. From the
> example above, I would have expected at least 1 WAL file named
> 00000001000000000000223387 to be in the backups directory.
>
> My questions are:
> 1. Is this normal behavior? (perhaps no activity in the DB to cause a WAL
> file write during the backup?)
> 2. If I try to restore the DB without this WAL file, will the restore
> fail?
>
> Thanks in advance
>
> Drew
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: steve@outtalimits.com.au, windsurferdrew-pg@yahoo.com
Subject: Re: WAL files during a backup
In-Reply-To: <7d15abe81b5970cf29b154bb23ac3ed6@127.0.0.1>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox