X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 243FF9FB391 for ; Thu, 13 Jul 2006 13:17:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 15425-07 for ; Thu, 13 Jul 2006 13:17:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 3ACAD9FB2B0 for ; Thu, 13 Jul 2006 13:17:27 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Thu, 13 Jul 2006 16:17:26 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 13 Jul 2006 11:17:26 -0500 Subject: Re: 8.1 Unique Index Issue/Bug??? From: Scott Marlowe To: Chris Hoover Cc: pgsql-admin@postgresql.org In-Reply-To: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com> References: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1152807446.14241.81.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Thu, 13 Jul 2006 11:17:26 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/88 X-Sequence-Number: 22334 On Thu, 2006-07-13 at 09:40, Chris Hoover wrote: > I am having what appears to be a bug with unique indexes on 8.1.3. > > I have created a new table. > > create table payer_835 ( > payer_id int8 not null default > nextval('payer_835_payer_id_seq'::regclass) primary key, > payer_name varchar(50) not null, > payer_trn03 varchar(10) not null, > payer_trn04 varchar(30), > sku_id int8 references skucode(sku_id) on delete > cascade on update cascade, > payer_billable boolean not null default true, > create_timestamp timestamp not null default now(), > last_mod_timestamp timestamp, > expire_timestamp timestamp > ); > > On this table, I have created a unique index on payer_trn03, > payer_trn04, and expire_timestamp. However, since the > expire_timestamp is normally null, the unique index does not appear to > be working. I have been able to enter two identical rows into this > table. > > Why is PostgreSQL not enforcing this index? This appears to be a > pretty major a bug? It would seem that you could have a unique index > across columns that might have a null in them. > > Here is the data from the table: > > COPY payer_835 (payer_id, payer_name, payer_trn03, payer_trn04, > sku_id, payer_billable, create_timestamp, last_mod_timestamp, > expire_timestamp) FROM stdin; > 1 CAHABA GBA-AL PART B 1630103830 \N 1 > t 2006-07-13 09:57: 52.834631 \N \N > 2 FEP 123456789 00402 1 t 2006-07-10 > 10:56:23 \N \N > 3 NC Medicaid 123123123 \N 1 t > 2006-07-10 10:56:41 \N \N > 4 CAHABA GBA-AL PART B 1630103830 \N 1 > t 2006-07-11 16:13:43.808181 2006-07-12 > 10:09:46.066204 \N > \. > > > Notice records 1 and 4 have identical data (as far as my unique index > is concerned), and the index it not complaining. But you have NULL expire_timestamps, and NULL <> NULL