From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Re: pgsql: Make CheckRequiredParameterValues() depend upon correct |
Date: | 2010-04-23 21:32:13 |
Message-ID: | 1272058333.4161.833.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Fri, 2010-04-23 at 16:44 -0400, Tom Lane wrote:
> There's no connection at all between what the GUC state
> was at shutdown and what it might be after starting again.
>
> A design that might work is
> (1) store the active value of wal_mode in pg_control (but NOT as part of
> the last-checkpoint-record image).
> (2) invent a new WAL record type that is transmitted when we change
> wal_mode.
>
> Then, slaves could check whether the master's wal_mode is high enough
> by looking at pg_control when they start plus any wal_mode_change
> records they come across.
Seems OK on standby side. On the primary there are some other points,
mentioned on other thread as to when we can change wal_mode.
> If we did this then we could get rid of those WAL record types that were
> added to signify that information had been omitted from WAL at specific
> times.
Please.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-04-23 22:23:39 | pgsql: Add missing optimizer hooks for function cost and number of rows. |
Previous Message | Robert Haas | 2010-04-23 21:27:21 | Re: [HACKERS] Re: pgsql: Make CheckRequiredParameterValues() depend upon correct |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2010-04-23 21:34:45 | Re: psql: Add setting to make '+' on \d implicit |
Previous Message | Robert Haas | 2010-04-23 21:29:09 | Re: recovery_connections cannot start (was Re: master in standby mode croaks) |