Re: Hot Standby: Caches and Locks
От | Simon Riggs |
---|---|
Тема | Re: Hot Standby: Caches and Locks |
Дата | |
Msg-id | 1225361602.3971.371.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Hot Standby: Caches and Locks (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Hot Standby: Caches and Locks
Re: Hot Standby: Caches and Locks |
Список | pgsql-hackers |
On Tue, 2008-10-21 at 15:06 +0100, Simon Riggs wrote: > We can't augment the commit/abort messages because > we must cater for non-transactional invalidations also, plus commit > xlrecs are already complex enough. So we log invalidations prior to > commit, queue them and then trigger the send at commit (if it > happens). Augmenting the commit messages seems like the better approach. It allows invalidation messages to be fired as they are read off the xlrec. Still need the additional message type to handle nontransactional invalidation. There are other messages possibly more complex than this already. -- Simon Riggs www.2ndQuadrant.comPostgreSQL Training, Services and Support
В списке pgsql-hackers по дате отправления: