Re: allowing wal_level change at run time - Mailing list pgsql-hackers

From Andres Freund
Subject Re: allowing wal_level change at run time
Date
Msg-id 20150819155622.GD10770@awork2.anarazel.de
Whole thread Raw
In response to Re: allowing wal_level change at run time  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 2015-08-19 17:51:47 +0200, Magnus Hagander wrote:
> That's doable - but what about manual base backups? And if they don't go
> away, what about the ones that are generated by the
> nightly/weekly/hourly/whatever "pg_basebackup -x" ones?

Good questions. I guess we could just make do_pg_start_backup() elevate
the WAL level (using a fixed slot name or some other mechanism) he first
time they're run, until there's explicit admin action.



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: allowing wal_level change at run time
Next
From: Tom Lane
Date:
Subject: Badly broken logic in plpython composite-type handling