Re: enable_resultcache confusion

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: enable_resultcache confusion
Date: 2021-07-15 15:43:59
Message-ID: 20210715154359.GB14882@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 12, 2021 at 11:47:27AM +1200, David Rowley wrote:
> On Mon, 12 Jul 2021 at 03:22, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > | This is useful if only a small percentage of rows is checked on
> > | the inner side and is controlled by <xref
> > | linkend="guc-enable-resultcache"/>.
>
> You might be right there, but I'm not too sure if I changed that that
> it might cause a mention of the rename to be missed in the changes
> since beta2 notes.

The commit will appear in the PG 14 git log, and someone will then see
the rename is part of the changes since the previous beta. Also, when
the release notes "as of" date is updated, all commits since the
previous "as of" date will be reviewed. Yes, someone might try to
update the release notes for this change and see it was already done,
but that is easily handled.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

If only the physical world exists, free will is an illusion.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2021-07-15 15:46:08 Re: psql - add SHOW_ALL_RESULTS option
Previous Message Dave Cramer 2021-07-15 15:43:20 Re: pg_upgrade does not upgrade pg_stat_statements properly