| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Alvaro Herrera <alvherre(at)surnet(dot)cl>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A 2 phase commit weirdness |
| Date: | 2005-05-27 15:12:06 |
| Message-ID: | 14918.1117206726@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnaka(at)iki(dot)fi> writes:
> Looking at the sequence, at least the relcache init file stuff looks if
> not broken at least a bit heavy-handed...
I was planning to change that ;-) ... using separate 2PC action records
for the relcache init file actions would make it much better.
> Now consider this scenario:
> backend A: Do updates that cause an init file invalidation
> backend A: Commit begins
> backend A: unlink init file
> backend B starts and recreates init file
> backend A: send inval message
> backend C starts and reads the now stale init file
No problem, because C will receive A's inval messages after that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-27 15:28:11 | Re: rendezvous |
| Previous Message | Tom Lane | 2005-05-27 15:09:38 | Re: foreign keys and RI triggers |