Andres Freund <[email protected]> writes:
> I wonder if the most natural way to express this wouldn't be to have a
> heavyweight lock for every 2pc xact
> 'slot'. ResourceOwnerRelease(RESOURCE_RELEASE_LOCKS) should be scheduled
> correctly to make error handling for this work.
That seems like not a bad idea. Could we also use the same lock to
prevent concurrent attempts to commit/rollback the same already-prepared
transaction? I forget what we're doing to forestall such cases right now.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
