Re: pg_plan_advice

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_plan_advice
Date: 2026-03-18 22:26:42
Message-ID: 1072503.1773872802@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Mar 18, 2026 at 4:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-03-18 22:31:19 Re: Initial COPY of Logical Replication is too slow
Previous Message Zsolt Parragi 2026-03-18 22:23:35 Re: meson vs. llvm bitcode files