| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Controlling hot standby |
| Date: | 2009-01-23 16:34:32 |
| Message-ID: | 4979F198.7050705@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Simon Riggs wrote:
>> On Fri, 2009-01-23 at 11:28 -0300, Alvaro Herrera wrote:
>
>>> 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?
>
> Would it slow down the normal recovery after a crash if I don't have any
> slaves?
Not in any meaningful way, I'd imagine.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-01-23 16:35:03 | Re: Controlling hot standby |
| Previous Message | Alvaro Herrera | 2009-01-23 16:28:26 | Re: Controlling hot standby |