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

Re: [BUGS] UNIQUE constraint no longer works under 6.5.1

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Dalphin <mdalphin(at)amgen(dot)com>, pgsql-bugs(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [BUGS] UNIQUE constraint no longer works under 6.5.1
Date: 1999-08-14 23:45:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
> > Interesting.  Playing with some variants of your example shows that
> > UNIQUE works fine *unless* there is another column marked PRIMARY KEY.
> > Then the UNIQUE constraint is ignored.  Looks like a simple logic bug in
> > the table-definition expander.
> > A look at the CVS logs reveals this apparently related entry for
> > parser/analyze.c:
> > revision 1.102
> > date: 1999/05/12 07:17:18;  author: thomas;  state: Exp;  lines: +68 -24
> > Fix problem with multiple indices defined if using column- and table-
> >  constraints. Reported by Tom Lane.
> > Now, check for duplicate indices and retain the one which is a primary-key.
> Yow! The problem reported earlier (by you, so you share some blame! ;)
> was that if one specified a primary key *and* a unique constraint, and
> they both pointed to the same column, then you got two indices
> created. So I tried to go through the list of indices and drop any
> which seemed to be the same as the primary key index.

OK, the immediate problem was due to a cut and paste typo (I was
comparing column names to decide if indices were identical, and the
pointer to the name was set to be the same for both index elements).

But, the code which was in there was always a bit wimpy; it only
checked for duplicate indices if they both had only one column. I've
modified it to (I think) check for any number of columns, so
constraints like

  create table t1 (i int, j int, unique(i,j), primary key(i,j))

should also work correctly by swallowing the "unique" index.

Here is a patch, to be applied in src/backend/parser/. Let me know if
it fixes your problem and any other cases you can think of, and I'll
apply it to the tree(s).

                      - Thomas

Thomas Lockhart				lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

Attachment: analyze.c.patch
Description: text/plain (2.5 KB)

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1999-08-15 04:35:52
Subject: Re: [HACKERS] How to get 'psql -q' runs really quiet ?
Previous:From: Hub.Org News AdminDate: 1999-08-14 23:19:31

pgsql-bugs by date

Next:From: Norman StevensDate: 1999-08-15 21:54:10
Subject: postgres bug
Previous:From: Hub.Org News AdminDate: 1999-08-14 23:17:51

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