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 20150819133411.GB5394@awork2.anarazel.de
Whole thread Raw
In response to Re: allowing wal_level change at run time  (Magnus Hagander <magnus@hagander.net>)
Responses Re: allowing wal_level change at run time  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 2015-08-19 10:49:46 +0200, Magnus Hagander wrote:
> What happens "the first time"? Meaning I'm on wal_level=minimal and take a
> base backup. Then when the replica first connects 10 minutes later, it
> needs WAL back in time, which was logged at wal_level=minimal.

> So you'd need to bump it up whenever a base backup is done -- but then you
> can't drop it back down again or your base backup will be useless.

> Or am I missing something?

Nope. Requiring pg_basebackup to automatically create such a
'non-reserving' slot doesn't seem to be too bad to me.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: allowing wal_level change at run time
Next
From: Kevin Grittner
Date:
Subject: Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows