Skip site navigation (1) Skip section navigation (2)

Re: small exclusion constraints patch

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: small exclusion constraints patch
Date: 2010-05-30 03:55:02
Message-ID: AANLkTim7B8Y4SuG3IngLCKw0ZvvUVavTESePwy_695pU@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Sat, May 29, 2010 at 11:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sat, May 29, 2010 at 6:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Or, to put it differently: if nobody's done that in the past twenty
>>> years, why is it likely to happen before 9.1?
>
>> Hmm.  Well suppose we bet a dollar on whether that will happen or not.
>>  In fact, if you promise not to read
>> http://archives.postgresql.org/pgsql-hackers/2010-05/msg01175.php I'll
>> make it two dollars.
>
> Yes, I've seen Jeff's example.  It's a cute hack but somehow I doubt
> that there is going to be a land rush to implement such things.
> Can you point to any pre-existing example where anyone actually asked
> for the ability to do that?

I've often wished for the ability to constrain a tale to hold just one
row, so I don't find that use case implausible at all.  As to whether
Jeff's use case is a cute hack or something that people will really
want to do, I think the jury's still out on that one.  But I don't
think we should make it not work unless we have a concrete reason, and
I haven't heard one yet.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-05-30 04:44:22
Subject: Re: Is there anyway to get list of table name, before raw parser is analyze?
Previous:From: Tom LaneDate: 2010-05-30 03:54:52
Subject: Re: Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group