From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Chris Lowder <clowder(at)hey(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 11.7. Indexes on Expressions |
Date: | 2021-12-22 22:06:12 |
Message-ID: | CAKFQuwZ_JgsW=hPi+asmaZqJ+kzi-mOCSC45RUbOZHQUCeJ_wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Dec 22, 2021 at 2:45 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Wed, Dec 22, 2021 at 02:40:12PM -0700, David G. Johnston wrote:
> > On Fri, Dec 17, 2021 at 2:43 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > I am attaching an updated patch which mentions non-HOT updates for
> > expression indexes.
> >
> >
> > Thanks. I'm a bit concerned that before this patch the only place we
> mentioned
> > HOTin the docs is in the appendix acronym listing which points to the
> readme
> > file in the source code.
>
> Uh, I had a similar concern and found these cases:
>
> monitoring.sgml: Number of rows updated (includes HOT
> updated rows)
> monitoring.sgml: Number of rows HOT updated (i.e., with no
> separate index
>
> Not sure what else we can do --- it would be odd to explain it in the
> expression index docs.
>
>
Found another one:
https://www.postgresql.org/docs/current/btree-implementation.html
"...(where most individual updates cannot apply the HOT optimization."
Make the acronym HOT in all these places take the reader to the acronym
page, and add a brief description there so they don't need to consume the
readme file?
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-12-22 22:09:53 | Re: 11.7. Indexes on Expressions |
Previous Message | Bruce Momjian | 2021-12-22 21:45:58 | Re: 11.7. Indexes on Expressions |