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 9D7EE9FB3EC for ; Thu, 13 Jul 2006 12:55:30 -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 14443-03-2 for ; Thu, 13 Jul 2006 12:55:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id 6F22B9FB1D8 for ; Thu, 13 Jul 2006 12:55:25 -0300 (ADT) Received: from bell.credativ.de (p50895AE6.dip.t-dialin.net [80.137.90.230]) (using TLSv1 with cipher EXP1024-RC4-SHA (56/128 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 7F43DD75FA; Thu, 13 Jul 2006 17:55:24 +0200 (CEST) From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: 8.1 Unique Index Issue/Bug??? Date: Thu, 13 Jul 2006 17:55:26 +0200 User-Agent: KMail/1.9.1 Cc: "Chris Hoover" References: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com> In-Reply-To: <1d219a6f0607130740g7fe13967t48c77a64fde977aa@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607131755.27335.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200607/94 X-Sequence-Number: 22340 Am Donnerstag, 13. Juli 2006 16:40 schrieb Chris Hoover: > 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. This behavior is correct according to the SQL standard, as two null values are not considered equal. -- Peter Eisentraut http://developer.postgresql.org/~petere/