| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Replication parameters in recovery.conf |
| Date: | 2017-12-06 04:31:12 |
| Message-ID: | CAB7nPqRP+Nb3LEphoaZNxw-eQhX8TngvvU2HS5k4MAwtm2A2gQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Dec 6, 2017 at 11:19 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> The reasons for this are basically all historical and we are trying to
> get rid of it (by moving these settings to postgresql.conf, mostly). So
> I don't think we need to spend a lot of time rationalizing this at this
> point.
Yeah, there are as well parameters that could get removed on the way,
like hot_standby for example. Most deployments don't use it to off
these days, and in Postgres 10 this moves makes even more sense as
wal_level = replica maps to both "archive" and "hot_standby", but
means the latter.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hmidi slim | 2017-12-06 14:37:21 | Why the planner does not use index for a large amount of data? |
| Previous Message | Peter Eisentraut | 2017-12-06 02:19:55 | Re: Replication parameters in recovery.conf |