| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, devrim(at)gunduz(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Controlling hot standby |
| Date: | 2009-01-23 18:00:16 |
| Message-ID: | 1232733616.2327.1239.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-01-23 at 10:35 -0600, Kevin Grittner wrote:
> >>> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > Simon Riggs wrote:
> >>
> >> 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?
>
> And how about during "traditional" PITR recovery?
It is possible that it might slow down a traditional PITR recovery. But
we enable the bgwriter to do checkpoints if we have it enabled, which
were a major cause of slow down during PITR anyway.
There are considerable benefits to having it turned on during PITR
Please read this to see why
http://wiki.postgresql.org/wiki/Hot_Standby#Dynamic_Control_of_Recovery
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-01-23 18:08:05 | Re: autovacuum and reloptions |
| Previous Message | Simon Riggs | 2009-01-23 17:57:28 | Re: Controlling hot standby |