I haven't played with PITR, but I believe that if PostgreSQL doesn't get the right return code from the archive_command it will keep the WAL files around; maybe that's the problem.
On Wed, Dec 14, 2005 at 10:57:38AM +0100, [EMAIL PROTECTED] wrote: > Hello to all ... > I'm trying to install a backup system for my Postgresql 8.1.1 (on windows xp) > using 3 wal files. > > So i change these parameters in postgresql.conf > checkpoint_segments = 3 > archive_command = 'copy "%p" "D:/PostgreSQL/backup/%f"' > > I stop the database service and then restart it ... > > Before restart i have 1 wal now i have 1 wal file ... > > I start to generate data to populate wal files and postgres start to generate > new wal files and copy them to the destination folder. > > The problem is that files number don't stop to increase, now i have 10 wal > files in pg_xlog and 9 files in backup folder ... > why the backup files don't be deleted ? > > thanks a lot in advance ... > > Fabio > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(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
