From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Further Hot Standby documentation required |
Date: | 2010-05-03 11:18:50 |
Message-ID: | 4BDEB11A.7070204@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 <literal>minimal</>, which writes only the
>> information needed to recover from a crash or immediate shutdown.
>> <literal>archive</> adds logging required for WAL archiving, and
>> <literal>hot_standby</> further adds information required to run
>> read-only queries on a standby server."
>>
>> Want to propose a better wording?
>
> "so at least archive level"
>
> changed to
>
> "so a setting of either archive or hot_standby"
>
> That way there is no concept of an ordering required to understand the
> sentence because it is explicit.
Ok, changed along those lines.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2010-05-03 13:01:45 | Re: missing file in git repo |
Previous Message | Magnus Hagander | 2010-05-03 10:42:55 | Re: missing file in git repo |