pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedReplication parameters in recovery.conf
3+ messages / 3 participants
[nested] [flat]
* Replication parameters in recovery.conf
@ 2017-12-01 11:12 Aleksandr Parfenov <a.parfenov@postgrespro.ru>
0 siblings, 1 reply; 3+ messages in thread
From: Aleksandr Parfenov @ 2017-12-01 11:12 UTC (permalink / raw)
To: pgsql-docs
Hello,
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?
--
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Replication parameters in recovery.conf
@ 2017-12-06 02:19 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
parent: Aleksandr Parfenov <a.parfenov@postgrespro.ru>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Eisentraut @ 2017-12-06 02:19 UTC (permalink / raw)
To: Aleksandr Parfenov <a.parfenov@postgrespro.ru>; 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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Replication parameters in recovery.conf
@ 2017-12-06 04:31 Michael Paquier <michael.paquier@gmail.com>
parent: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 3+ messages in thread
From: Michael Paquier @ 2017-12-06 04:31 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>; +Cc: Aleksandr Parfenov <a.parfenov@postgrespro.ru>; pgsql-docs
On Wed, Dec 6, 2017 at 11:19 AM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-12-06 04:31 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-12-01 11:12 Replication parameters in recovery.conf Aleksandr Parfenov <a.parfenov@postgrespro.ru>
2017-12-06 02:19 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
2017-12-06 04:31 ` Michael Paquier <michael.paquier@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox