Josh Berkus <[EMAIL PROTECTED]> writes:
>> No. I want to know what the subordinate does when it's promised to
>> commit and the co-ordinator never responds. AFAICS the subordinate
>> is screwed --- it can't commit, and it can't abort, and it can't expect
>> to make progress indefinitely on other work while it's holding locks
>> for the not-quite-committed transaction.
> Anyway, I would vote for a first implemenation for 2PC which addressed the
> commit-then-crash issue in some expedient-but-not-reliable way, and putting
> 2PC in /contrib with a "not for production use" warning. Some people will
> use it in production anyway, and hopefully one or more of them will put in
> the dozens of hours required to make it reliable.
Putting in "dozens of hours" is not the issue here --- the problem is
that there isn't any solution in sight, and I'm not eager to go down a
path that has an obvious dead end.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
