Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jNFCf-00084I-BY for pgsql-docs@arkaria.postgresql.org; Sat, 11 Apr 2020 12:25:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jNFCc-0007AK-4t for pgsql-docs@arkaria.postgresql.org; Sat, 11 Apr 2020 12:25:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jNFCb-0007AD-VD for pgsql-docs@lists.postgresql.org; Sat, 11 Apr 2020 12:25:37 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jNFCY-0006LT-Nh for pgsql-docs@postgresql.org; Sat, 11 Apr 2020 12:25:37 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jNFCW-0008Jv-9p; Sat, 11 Apr 2020 08:25:32 -0400 Date: Sat, 11 Apr 2020 08:25:32 -0400 From: Bruce Momjian To: Tom Lane Cc: PostgreSQL-documentation Subject: Re: pgsql: doc: add examples of creative use of unique expression indexes Message-ID: <20200411122532.GE24988@momjian.us> References: <2304.1586532634@sss.pgh.pa.us> <20200410214821.GC24988@momjian.us> <13031.1586560889@sss.pgh.pa.us> <20200411001709.GD24988@momjian.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="VywGB/WGlW4DM4P8" Content-Disposition: inline In-Reply-To: <20200411001709.GD24988@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --VywGB/WGlW4DM4P8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 10, 2020 at 08:17:09PM -0400, Bruce Momjian wrote: > On Fri, Apr 10, 2020 at 07:21:29PM -0400, Tom Lane wrote: > > Bruce Momjian writes: > > > I agree with your analysis. I still want to have some mention that > > > partial indexes can be used to create single-NULL columns, which might > > > be required for compatibility with other databases. Attached is an > > > updated patch which removes the previous commit but adds a mention of > > > this. > > > > The single-null thing is probably a useful example, but please make > > it an actual separate example, or at least its own para outside the > > existing sections. > > > > Also, the existing example demonstrating that seems overcomplicated; > > why not just > > > > create unique index ... (1) where (foo is null); > > I ended up using "true" since that is ony one byte; patch attached. [ thread moved to docs] I now remember that I wrote the first IS NULL in: CREATE UNIQUE INDEX tests_target_one_null ON tests ((target IS NULL)) WHERE target IS NULL; in hope that if someone is looking for the null value in the column, the IS NULL would allow the index to be used to find it, while 1 or true would not. Also, I think the most popular use for this ability would be for multi-column indexes where you want only one NULL value for a combination of columns, e.g.: CREATE UNIQUE INDEX tests_target_one_null ON test (x, (y IS NULL)) WHERE y IS NULL; I have added that. It also hows the use of columns and expressions in the same index. Proposed patch attached. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + --VywGB/WGlW4DM4P8 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="index.diff" diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml index 1be209a2fe..2790fb2a89 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -705,15 +705,6 @@ CREATE INDEX test1_lower_col1_idx ON test1 (lower(col1)); - - Expression indexes also allow control over the scope of unique indexes. - For example, this unique index prevents duplicate integer values from - being stored in a double precision-typed column: - -CREATE UNIQUE INDEX test1_uniq_int ON tests ((floor(double_col))) - - - If we were to declare this index UNIQUE, it would prevent creation of rows whose col1 values differ only in case, @@ -956,16 +947,22 @@ CREATE UNIQUE INDEX tests_success_constraint ON tests (subject, target) successful tests and many unsuccessful ones. - - This index allows only one null in the indexed column by using a - partial index clause to process only null column values, and using - an expression index clause to index true instead - of null: + + + + This index allows only one null in the indexed column by using a + partial index clause to process only null column values, and using + an expression index clause to index true instead + of null: CREATE UNIQUE INDEX tests_target_one_null ON tests ((target IS NULL)) WHERE target IS NULL; - - + This index allows only one null value for each value in the first + referenced column: + +CREATE UNIQUE INDEX tests_combo_one_null ON tests (col1, (target IS NULL)) WHERE target IS NULL; + + Finally, a partial index can also be used to override the system's --VywGB/WGlW4DM4P8--