Re: FW: Setting up of PITR system.

Are you talking about tar-ing your completed WAL logs, or the file-system
database directory?

1. If you're talking about tar-ing archived WAL logs - the logs you're
archiving shouldn't be changing, as they should be archived outside of your
PG data directory structure (with the use of archive_command) - perhaps your
archive command should move the files out of the pg_xlog directory BEFORE
tar-ing.

2. If you're talking about logs changing while you're tar-ing your PG data
directory, you shouldn't be including your pg_xlog directory in the archive,
as long as you've got all the WAL logs available AFTER the dump is done,
then it'll fix any inconsistencies in the data when you do the restore.

Hope this helps

Andy

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Sriram Dandapani
Sent: Friday, 31 March, 2006 7:19 pm
To: Jim C. Nasby; Tom Lane
Cc: andy(dot)shellam(at)mailnetwork(dot)co(dot)uk; Rajesh Kumar Mallah;
pgsql-admin(at)postgresql(dot)org
Subject: Re: FW: [ADMIN] Setting up of PITR system.

We have high volume inserts happening with wal files being generated
very rapidly. Will the fact that the files change as the tar happens
have any effect at all on the recovery..assuming all the appropriate wal
archive logs are available.

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Jim C. Nasby
Sent: Friday, March 31, 2006 10:11 AM
To: Tom Lane
Cc: andy(dot)shellam(at)mailnetwork(dot)co(dot)uk; 'Rajesh Kumar Mallah';
pgsql-admin(at)postgresql(dot)org
Subject: Re: FW: [ADMIN] Setting up of PITR system.

On Wed, Mar 29, 2006 at 09:46:30AM -0500, Tom Lane wrote:
> It definitely is a pain in the neck that GNU tar complains about files
> changing underneath it --- I've looked for a way to disable that, or
at
> least reduce it to a warning instead of an error condition, but gtar
> doesn't seem to have such a switch. You should try alternative backup
> tools such as cpio or rsync.

Or you might submit a patch to GNU tar. There's also a BSD version of
tar, it's on at least FreeBSD (not sure if there's a stand-alone version
avaiable). It might not suffer from the same problem, though I haven't
tried it. I do have a machine I could try it with if that would help.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

!DSPAM:14,442d72c535048270212230!