| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| Date: | 2010-02-12 15:27:20 |
| Message-ID: | 4B757358.1020007@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas wrote:
> Furthermore, if you're wanting to use pg_standby, you might be
> forgiven for thinking that you should set standby_mode = on; but in
> fact that's exactly the wrong thing to do.
Yeah, I think that's the main weakness of the name "standby_mode". It's
pretty descriptive otherwise, we call that mode of operation "standby"
everywhere, and always have.
I'm not sure I dare to say this out loud after Simon's previous
outburst, but removing or renaming pg_standby would help with that...
> One possibility that occurs to me is that we could call it something
> like integrated_standby; but I'm not attached to that.
Anything with the word 'standby' in it suffers from the same problem,
maybe not as badly but still.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-12 15:28:33 | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| Previous Message | Robert Haas | 2010-02-12 15:14:41 | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-12 15:28:33 | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
| Previous Message | Robert Haas | 2010-02-12 15:24:40 | Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH] |