Re: enable_resultcache confusion - Mailing list pgsql-hackers

From David Rowley
Subject Re: enable_resultcache confusion
Date
Msg-id CAApHDvomcpa28WvrpHA06m+F2JnKn4JuHJmU2sHz2Xcd84YcVg@mail.gmail.com
Whole thread Raw
In response to Re: enable_resultcache confusion  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: enable_resultcache confusion  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: enable_resultcache confusion  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Mon, 12 Jul 2021 at 03:22, Justin Pryzby <pryzby@telsasoft.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.

Additionally, I was unsure about touching typedefs.list. In the patch
I changed it, but wasn't too sure if that was the correct thing to do.
In normal circumstances, i.e writing new code, I'd not touch it.

David



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Protect against possible memory corruption (src/backend/access/nbtree/nbtxlog.c)
Next
From: Alvaro Herrera
Date:
Subject: Re: row filtering for logical replication