Re: Two weeks to feature freeze
| От | Tom Lane |
|---|---|
| Тема | Re: Two weeks to feature freeze |
| Дата | |
| Msg-id | 16168.1056341196@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Two weeks to feature freeze (Sailesh Krishnamurthy <sailesh@cs.berkeley.edu>) |
| Ответы |
Re: Two weeks to feature freeze
|
| Список | pgsql-hackers |
Sailesh Krishnamurthy <sailesh@cs.berkeley.edu> writes:
> I'm not sure if I understand Tom's beef - I think he is concerned
> about what happens if a subordinate does not respond to a prepare
> message. I would assume that the co-ordinator would not let the commit
> go through until it has received confirmations from every
> subordinate.
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.
regards, tom lane
В списке pgsql-hackers по дате отправления: