On Mon, 2010-05-03 at 23:28 +0300, Heikki Linnakangas wrote:
> Sorry, I just didn't have the time & energy to figure out what to do
> about that. Feel free to fix as you see fit.
Yeh, I sometimes feel like that towards other hacker's comments as well.
--
Simon Riggs www.2ndQuadrant.c
Simon Riggs wrote:
> On Mon, 2010-05-03 at 10:50 +0100, Simon Riggs wrote:
>> On Mon, 2010-05-03 at 12:17 +0300, Heikki Linnakangas wrote:
>>
> * wal_level doesn't describe what the impacts are on a standby if the
> level is changed on the primary, nor is there a caution or a warning of
>>>
On Mon, 2010-05-03 at 10:50 +0100, Simon Riggs wrote:
> On Mon, 2010-05-03 at 12:17 +0300, Heikki Linnakangas wrote:
>
> > >> * wal_level doesn't describe what the impacts are on a standby if the
> > >> level is changed on the primary, nor is there a caution or a warning of
> > >> any kind. For ex
Simon Riggs wrote:
> Doesn't this new behaviour prevent startup-from-a-shutdown-checkpoint?
No.
* wal_level doesn't explicitly describe that the levels are in sequence
and that hot_standby is a superset of archive.
>> It does say:
>> "The default value is minimal, which writes only the
On Mon, 2010-05-03 at 12:17 +0300, Heikki Linnakangas wrote:
> >> * wal_level doesn't describe what the impacts are on a standby if the
> >> level is changed on the primary, nor is there a caution or a warning of
> >> any kind. For example, if a standby is setup with hot_standby = on and
> >> the
Bruce Momjian wrote:
> Simon Riggs wrote:
>> * wal_level = 'hot_standby' doesn't mention that the second parameter
>> also needs to be set, nor is there a xref.
Fixed.
>> * wal_level doesn't describe what the impacts are on a standby if the
>> level is changed on the primary, nor is there a cauti
Simon Riggs wrote:
>
> Recent changes to parameters aren't yet sufficiently well documented and
> I'd like to see this improved by the authors of those patches. I accept
> the behaviour changes, but we need full docs to explain them.
>
> * hot_standby doesn't mention that wal_level = hot_standby
Recent changes to parameters aren't yet sufficiently well documented and
I'd like to see this improved by the authors of those patches. I accept
the behaviour changes, but we need full docs to explain them.
* hot_standby doesn't mention that wal_level = hot_standby is also
required, nor is there
