On Wed, Apr 19, 2006 at 03:51:27AM +0200, Florian G. Pflug wrote:
> Tom Lane wrote:
> >elein <[EMAIL PROTECTED]> writes:
> >>I think I want to:
> >> create unique index pk on table tbl (keyp1, keyp2);
> don't you want
> create unique inde pk on table tbl (keyp1, keyp2) where keyp3 is null
> here?
>
> >> create unique index range on table tbl (keyp1, keyp2, keyp3) where
> >> keyp3 is not null;
> >
> >>Are these indexes redundant given uniqueness requirement and the type of
> >>queries
> >>that will be run against the table?
>
> greetings, Florian Pflug
>
Yes, you are right. I ended up creating a unique constraint on the three
parts of the key and a unique index on keyp1, keyp2 where keyp3 is null.
I think this will cover all cases as simply as possible.
Thanks,
--elein
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
