Re: pg_plan_advice - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_plan_advice
Date
Msg-id 1072503.1773872802@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_plan_advice  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_plan_advice
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Mar 18, 2026 at 4:44 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It looks like the appearance of "Supplied Plan Advice:" depends
>> on whether the prepared query's plan got regenerated or not.
>> I'm not sure if this represents a bug (ie undesirable behavior) or
>> it's just that the test is being insufficiently careful about
>> being reproducible.

> Well, that's embarrassing: it's a copy-and-paste error. The test
> prepares and executes pt1, then prepares and executes pt2, then
> prepares pt3 and executes pt1, then prepares pt4 and execute p2. pt3
> and pt4 are never used for anything. Also there's a related typo in a
> comment. See attached.

Ah ... so the observed behavior is because if pt2 does get replanned,
that happens with a different always_store_advice_details setting
than it used originally?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Zsolt Parragi
Date:
Subject: Re: meson vs. llvm bitcode files
Next
From: Masahiko Sawada
Date:
Subject: Re: Initial COPY of Logical Replication is too slow