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: Hot standby, prepared xacts, locks |
Date: | 2009-10-21 17:00:40 |
Message-ID: | 1256144440.492.5359.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2009-10-21 at 19:37 +0300, Heikki Linnakangas wrote:
> So, I'm quite eager to just revert all those lock_twophase_recover()
> changes, and always rely on the "grant lock to dummy proc, then
> release
> it in startup process" method. If we don't want to rely on that,
> PostPrepare_Locks is an example of how to transfer lock ownership from
> one process to another correctly.
Yes, I realised after I wrote it that PostPrepare already does that
switch, just been busy with other stuff to switch over the code.
I think we do need some special code because of handling whole lock
queues. i.e. if there is a backend requesting an AEL but a prepared xact
has it, the lock queue will initially be Backend->Startup and needs to
end up looking like Backend->DummyProc.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel ROZE | 2009-10-21 17:04:41 | Re: URL Managment - C Function help |
Previous Message | Andrew Dunstan | 2009-10-21 16:59:16 | Re: URL Managment - C Function help |