Re: Move WAL warning
Magnus Hagander <magnus@hagander.net>
From: Magnus Hagander <magnus@hagander.net>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-02T17:00:42Z
Lists: pgsql-hackers
Attachments
- stop_backup_warning.patch (text/x-patch) patch
On Wed, Feb 2, 2011 at 17:43, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > On 02.02.2011 16:36, Magnus Hagander wrote: >> >> When running pg_basebackup with -x to include all transaction log, the >> server will still throw a warning about xlog archiving if it's not >> enabled - that is completely irrelevant since pg_basebackup has >> included it already (and if it was gone, the base backup step itself >> will fail - actual error and not warning). >> >> This patch moves the warning from do_pg_base_backup to pg_base_backup, >> so it still shows when using the explicit function calls, but goes >> away when using pg_basebackup. > > For the sake of consistency, how about moving the "pg_stop_backup complete, > all required WAL segments have been archived" notice too? Well, it goes out as a NOTICE, so by default it doesn't show.. But yeah, for code-consistency it makes sense. Like so, then. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/