| From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 10:54:17 |
| Message-ID: | 4C0243D9.9070202@cs.helsinki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2010-05-30 06:55 +0300, Robert Haas wrote:
> On Sat, May 29, 2010 at 11:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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 I pointed out in
http://archives.postgresql.org/pgsql-hackers/2010-05/msg01177.php , you
can already do that.
Having said that, I also think that supporting <> in exclusion
constraints would be useful. I can't come up with a real-world use case
right now though.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-05-30 11:00:03 | server authentication over Unix-domain sockets |
| Previous Message | Andres Freund | 2010-05-30 09:56:16 | Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up |