Re: pg_*_advice: tsv load failure, etc.

From: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dongpo Liu <poe(dot)liu(at)pm(dot)me>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_*_advice: tsv load failure, etc.
Date: 2026-10-12 06:08:47
Message-ID: CAKZiRmz-L=YufpYLZFqqiwWsXeWPYNj2QjEEoNd583CV+wziEg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 9, 2026 at 9:15 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Sun, Oct 4, 2026 at 8:38 AM Dongpo Liu <poe(dot)liu(at)pm(dot)me> wrote:
> > The patch adds a paragraph to the Limitations section of pg_plan_advice
> > and a short pointer in pg_stash_advice. It says that advice is consulted
> > only at plan time, mentions DISCARD PLANS for the current session, and
> > refers to PREPARE for when other sessions re-plan.
>
> I think it's a good idea to add something to the documentation about
> this issue, but I'm not entirely convinced by this wording. In
> particular:
> [..patch..]

LGTM for me too, thanks!

-J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Tender Wang 2026-10-12 06:03:50 Wrong results from self-join elimination with different restriction operators