| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Controlling hot standby |
| Date: | 2009-01-23 12:43:30 |
| Message-ID: | 1232714610.2327.1177.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-01-23 at 14:28 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > On Fri, 2009-01-23 at 10:35 +0200, Heikki Linnakangas wrote:
> >> As the patch stands, there's no way to disable hot standby. The server
> >> always opens for read-only connections as soon as it can. That might not
> >> be what you want.
> >>
> >> I think we need a GUC to enable/disable hot standby. It would become
> >> handy if the unimaginable happens and there's a bug in the hot standby
> >> code that prevents a server from recovering.
> >
> > Currently recovery processing is only active during archive recovery,
> > never during crash recovery, for the above reason.
>
> Oh, ok. Is the bgwriter still launched in crash recovery,
Currently in the patch we never launch bgwriter in crash recovery.
> and do we
> start accepting connections as soon as the replay finishes, before the
> first checkpoint is finished?
Which means we never use "fast start" behaviour. We write a full
checkpoint and only then do we open for business normally.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2009-01-23 13:18:20 | [PATCH] reloptions - RELOPT_KIND_ALL |
| Previous Message | Teodor Sigaev | 2009-01-23 12:41:28 | Re: [PATCHES] GIN improvements |