Re: Exposing the Xact commit order to the user

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <robertmhaas(at)gmail(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>,<JanWieck(at)yahoo(dot)com>
Subject: Re: Exposing the Xact commit order to the user
Date: 2010-05-24 16:51:02
Message-ID: 4BFA682602000025000319BD@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:

> I think you're confusing two subtly different things.

The only thing I'm confused about is what benefit anyone expects to
get from looking at data between commits in some way other than our
current snapshot mechanism. Can someone explain a use case where
what Jan is proposing is better than snapshot isolation? It doesn't
provide any additional integrity guarantees that I can see.

> But the commit order is still the order the effects of those
> transactions have become visible - if we inserted a new read-only
> transaction into the stream at some arbitrary point in time, it
> would see all the transactions which committed before it and none
> of those that committed afterward.

Isn't that what a snapshot does already?

> your proposed fix sounds like it would be prohibitively expensive
> for many users. But can this actually happen?

How so? The transaction start/end logging, or looking at that data
when building a snapshot?

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-05-24 17:11:16 Re: Exposing the Xact commit order to the user
Previous Message Josh Berkus 2010-05-24 16:44:32 Re: Idea for getting rid of VACUUM FREEZE on cold pages