Re: Controlling hot standby - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Controlling hot standby
Date
Msg-id 1232724493.2327.1214.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Controlling hot standby  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Controlling hot standby  (Alvaro Herrera <alvherre@commandprompt.com>)
List 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.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] reloptions - RELOPT_KIND_ALL
Next
From: Tom Lane
Date:
Subject: Re: Pluggable Indexes