| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Controlling hot standby |
| Date: | 2009-01-23 15:28:13 |
| Message-ID: | 1232724493.2327.1214.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-01-23 at 11:28 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> >
> > On Fri, 2009-01-23 at 12:58 +0200, Devrim GÜNDÜZ wrote:
> > > On Fri, 2009-01-23 at 10:05 +0000, Simon Riggs wrote:
> > > > I'll add it now, default = on.
> > >
> > > Did you mean "off"?
> >
> > No, do you?
>
> Depends on the setting :-) It is "hot_standby=off" by default, right?
> I think having a double negative "disable_hot_standby=off" would be
> awkward.
It is on by default. Why would you want it "off" by default?
We want people to use the feature and turn it off only if they need to
for some reason.
It is only used during archive recovery, so it is already "off" if
you're using some other kind of replication.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-23 15:33:33 | Re: Pluggable Indexes |
| Previous Message | Tom Lane | 2009-01-23 15:19:37 | Re: [PATCH] reloptions - RELOPT_KIND_ALL |