Re: Transactional DDL, but not Serializable

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transactional DDL, but not Serializable
Date: 2011-03-25 18:01:48
Message-ID: 20110325180148.GP4116@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Joshua Berkus (josh(at)agliodbs(dot)com) wrote:
> That seemed unnecessary. Whether or not you approve of Stephen's solution, he is dealing with a real issue.

The solution felt, to me at least, to have a lot of parallel to an
index's indcheckxmin. We've dealt with this issue there and have a
precedent for how to deal with it. Based on discussions with other
folks it sounds like we may be forced to do it for constraints also, and
I think we'd want to try to deal with all of them in a similar way.

Perhaps the current solution for indexes is a hack and should be tossed
out with a wholesale replacment which solves all these problems, which
would certainly be quite a bit of work, but if that's necessary then
let's discuss it and get an idea down on a wiki somewhere about what
that should look like.

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-25 18:08:31 Re: 2nd Level Buffer Cache
Previous Message Joshua Berkus 2011-03-25 17:53:04 Re: Transactional DDL, but not Serializable