| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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 02:19:55 |
| Message-ID: | c359ca55-d30f-45d9-7119-f34a27be152e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 12/1/17 06:12, Aleksandr Parfenov wrote:
> Reading a documentation regarding recovery.conf file I found that the
> reason to store 'stand-by mode' configuration inside that file is not
> clear.
>
> IMHO, a little note in description of recovery.conf will clearify
> the situation. Something like "a stand-by is submode of recover mode"
> and that the file used during replication will help. Same as in
> recovery.conf.sample file will be fine too.
>
> What the community thinks about it?
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-06 04:31:12 | Re: Replication parameters in recovery.conf |
| Previous Message | Peter Eisentraut | 2017-12-06 02:15:05 | Re: MacPorts xsltproc is very slow? |