From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | None <espressobeanies(at)gmail(dot)com> |
Cc: | Pantelis Theodosiou <ypercube(at)gmail(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Need help finding all possible parameters for wal_level |
Date: | 2017-09-01 14:58:59 |
Message-ID: | CAKFQuwa7yHNmXoLk5Gp-Dc4NMinhEU5h6AZmVH_n-9OD1RUZFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Fri, Sep 1, 2017 at 7:46 AM, None <espressobeanies(at)gmail(dot)com> wrote:
> Well, so that's what doesn't make sense. Other documentation also
> indicates a 'hot_standby' setting and I'm looking to see if it can do
> 'warm_standby' as well. I was hoping for a complete list because it seems
> scattered right now.
>
The documentation is version specific. All of the values allowed for the
specified version are listed on that page. There is not and never was a
"warm_standby" value. The valid values for wal_level do not fully restrict
how one can setup their standby configuration but rather define the minimum
possible configuration (which is basically either cold or warn standby
depending on whether you decide to run an independent standby server full
time). The settings at
https://www.postgresql.org/docs/current/static/runtime-config-replication.html
are use if you wish to convert the warm standby into a hot standby. In
either case the relevant wal_level needs to be "replica". It was deemed
unnecessary to distinguish between "archive (cold/warn) and hot_standby" in
9.6 - in terms of what information was recorded in the WAL.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | None | 2017-09-01 15:11:35 | Re: Need help finding all possible parameters for wal_level |
Previous Message | Jerry Sievers | 2017-09-01 14:54:23 | Re: Need help finding all possible parameters for wal_level |