Skip site navigation (1)
Skip section navigation (2)
Currently, WAL files will be archived as soon as archive_command is set. IMHO, this is not desirable if no permanent backup is wanted, but only scheduled online backup because; it will flood the wal_archive destination with files that will never be used.
Peripheral Links
Header And Logo
|
Site Navigation
XLogArchivingActive
- From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
- To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: XLogArchivingActive
- Date: Thu, 25 May 2006 13:00:56 +0200
- Message-id: <44758E68(dot)5060805(at)pse-consulting(dot)de>
Currently, WAL files will be archived as soon as archive_command is set. IMHO, this is not desirable if no permanent backup is wanted, but only scheduled online backup because; it will flood the wal_archive destination with files that will never be used.
I propose to introduce a GUC "permanent_archiving" or so, to select whether wal archiving happens permanently or only when a backup is in progress (i.e. between pg_start_backup and pg_stop_backup).
Regards, Andreas
- Follow-Ups:
- Re: XLogArchivingActive
- From: Tom Lane
- Re: XLogArchivingActive
- Prev by Date: Re: compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- Next by Date: Re:
- Previous by thread: [no subject]
- Next by thread: Re: XLogArchivingActive
- Indexes: