From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | farmernick-pg(at)varteg(dot)nz, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: 11.7 Indexes on Expressions: editorial correction |
Date: | 2020-05-21 23:50:28 |
Message-ID: | 20200521235028.GA24478@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, May 19, 2020 at 10:32:01AM -0400, Tom Lane wrote:
> PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> > The paragraph that begins "If we were to declare this index UNIQUE,..."
> > refers to the index test1_lower_col1_idx, not to the test1_uniq_int index it
> > currently follows. It would appear the latter example was spliced into the
> > middle of discussing the former.
>
> Yes, this was complained of before:
>
> https://www.postgresql.org/message-id/flat/E1ikvbp-0005jW-E9%40gemulon.postgresql.org
>
> I remain of the opinion that we'd be best off to just revert
> a9760d0f3 altogether. Bruce's last proposal mostly did that,
> but it still insisted on muddying an existing example with an
> unrelated comment.
Muddy patch applied. ;-) I am open to clarifying it but I think we
need something in our docs about this idea.
--
Bruce Momjian <bruce(at)momjian(dot)us> 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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2020-05-22 00:28:56 | Re: explanation for random_page_cost is outdated |
Previous Message | Bruce Momjian | 2020-05-21 23:49:41 | Re: pgsql: doc: add examples of creative use of unique expression indexes |