RE: ADD CONSTRAINT behaviour question

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: ADD CONSTRAINT behaviour question
Date: 2001-07-09 01:49:03
Message-ID: ECEHIKNFIMMECLEBJFIGCEDHCBAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> You assume wrong.
>
> It's a bad idea to try to develop backend code against back releases.

My bad. I'm at work at the moment and I tried it out here to rejig my
memory before posting. I do remember testing it on HEAD at home and the
create table (.., unique, unique) doesn't duplicate.

Don't worry - it's being developed on HEAD - I was just trying to get out of
figuring out how to detect an already existing index across specified
columns. It's complicated.

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-07-09 01:50:02 Re: ADD CONSTRAINT behaviour question
Previous Message Christopher Kings-Lynne 2001-07-09 01:46:40 RE: Re: [GENERAL] Vacuum and Transactions