| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parameter name standby_mode |
| Date: | 2010-02-11 10:34:56 |
| Message-ID: | 1265884496.7341.1189.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2010-02-10 at 13:16 +0200, Heikki Linnakangas wrote:
> If they want to implement the warm standby using the (new) built-in
> logic to keep retrying restore_command, they would set
> standby_mode='on'. standby_mode='on' doesn't imply streaming replication.
The docs say "If this parameter is on, the streaming replication is
enabled". So who is wrong?
ISTM that Joachim's viewpoint is right and that most people will be
confused about this.
I think we need something named more intuitively. Something that better
describes what action (i.e. a verb) will occur when this is set.
Suggestions: streaming_replication = on
We may need to split out various complexities into multiple parameters,
or have valued parameters, e.g. standby_mode = REPLICA.
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-02-11 10:37:37 | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Previous Message | Simon Riggs | 2010-02-11 10:10:32 | Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while |