| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mike Mascari <mascarm(at)mascari(dot)com>, Rod Taylor <rbt(at)rbt(dot)ca>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Two weeks to feature freeze |
| Date: | 2003-06-23 02:57:41 |
| Message-ID: | 200306230257.h5N2vfT16430@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I sure want two-phase commit. I don't remember it as being rejected,
> > and we certainly need it, independent of replication.
>
> Is 2PC a real-world solution to any real-world problem? I have never
> seen a satisfactory explanation of what you do when you've reported that
> you're ready to commit and no confirmation ever comes back. Sooner or
> later you must violate the protocol in one direction or the other (ie,
> commit without confirmation or roll back in violation of your promise
> of being able to commit).
>
> I think it's a cool-sounding phrase that does not actually work in
> practice.
I think 2PC can be used to build more complex features, like using dblink
for cross-db modification queries.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2003-06-23 03:00:39 | Re: O_DIRECT in freebsd |
| Previous Message | Sean Chittenden | 2003-06-23 02:46:56 | Re: O_DIRECT in freebsd |