Re: Hot Standby and deadlock detection
От | Heikki Linnakangas |
---|---|
Тема | Re: Hot Standby and deadlock detection |
Дата | |
Msg-id | 4B668560.2080808@enterprisedb.com обсуждение исходный текст |
Ответ на | Hot Standby and deadlock detection (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Hot Standby and deadlock detection
|
Список | pgsql-hackers |
Simon Riggs wrote: > The way this would work is if Startup waits on a buffer pin we > immediately send out a request to all backends to cancel themselves if > they are holding the buffer pin required && waiting on a lock. We then > sleep until max_standby_delay. When max_standby_delay = -1 we only sleep > until deadlock timeout and then check (on the Startup process). Should wake up to check for deadlocks after deadlock_timeout also when max_standby_delay > deadlock_timeout. max_standby_delay could be hours - we want to detect a deadlock sooner than that. Generally speaking, max_standby_delay==-1 codepath shouldn't be any different from the max_standby_delay>0 codepath. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: