Re: pg_plan_advice - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: pg_plan_advice
Date
Msg-id CAKFQuwbOt+19OBwKh91cKZyBP4RHuVuCtR8sKs4UH5QUu1GLew@mail.gmail.com
Whole thread Raw
In response to Re: pg_plan_advice  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers

On Wed, Jan 28, 2026 at 10:14 AM Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Jan 12, 2026 at 12:13 PM Robert Haas <robertmhaas@gmail.com> wrote:
> If not, I'll rearrange
> the series to move 0004 to the front, and plan to commit that first.

That rearrangement got done in v11, and I've now committed that patch
after fixing a few typos that I found. Cautiously, woohoo, but let's
see if anything breaks.

Here's v13. 

Documentation review patch attached.

Overall it flowed well.  Most of the changes are just typos or similar.

I found the idea of seeing "Disabled: true" to not make immediate sense.  I've left some comments near that section and plan to come back to it.

The comment about collector memory usage was duplicated more-or-less.  I kept the first, less loud, instance.

Removed the few uses of "we" in favor of pg_plan_advice being the actor.

David J.

Attachment

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: ERROR: failed to find conversion function from iso-8859-1 to text
Next
From: Alexander Lakhin
Date:
Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)