Re: Hot standby, recovery infra

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Hot standby, recovery infra
Дата
Msg-id 1233313877.8859.20.camel@ebony.2ndQuadrant
обсуждение исходный текст
Ответ на Re: Hot standby, recovery infra  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Hot standby, recovery infra  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
On Thu, 2009-01-29 at 14:21 +0200, Heikki Linnakangas wrote:
> It looks like if you issue a fast shutdown during recovery, postmaster 
> doesn't kill bgwriter.

Thanks for the report.

I'm thinking to add a new function that will allow crash testing easier.

pg_crash_standby() will issue a new xlog record, XLOG_CRASH_STANDBY,
which when replayed will just throw a FATAL error and crash Startup
process. We won't be adding that to the user docs...

This will allow us to produce tests that crash the server at specific
places, rather than trying to trap those points manually.

> Seems that reaper() needs to be taught that bgwriter can be active 
> during consistent recovery. I'll take a look at how to do that.
> 
> 
> BTW, the message "terminating connection ..." is a bit misleading. It's 
> referring to the startup process, which is hardly a connection. We have 
> that in CVS HEAD too, so it's not something introduced by the patch, but 
> seems worth changing in HS, since we then let real connections in while 
> startup process is still running.
> 
-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Hot standby, recovery infra
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Hot standby, recovery infra