Re: Two weeks to feature freeze

From: The Hermit Hacker <scrappy(at)postgresql(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 03:10:33
Message-ID: 20030623000919.W95856@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 22 Jun 2003, Bruce Momjian wrote:

> 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.

That was my understanding too ... as soon as you try and go distributed,
you need some method of ensuring that the data is constant across them all
...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-06-23 03:13:10 Re: O_DIRECT in freebsd
Previous Message Tom Lane 2003-06-23 03:05:52 Re: O_DIRECT in freebsd