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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
