Re: pg_plan_advice

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dian Fay <di(at)nmfay(dot)com>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_plan_advice
Date: 2025-12-15 16:37:43
Message-ID: CAOYmi+k4AyWCQHK=XVF99KVDuFkqxcADao61OWGLxu0nRYMONQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 12, 2025 at 10:09 AM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> Next bit of fuzzer feedback:

And another bit, but this time I was able to minimize into a
regression case, attached.

This comment in pgpa_identifier_matches_target() seems to be incorrect:

> /*
> * The identifier must specify a schema, but the target may leave the
> * schema NULL to match anything.
> */

But I don't know whether that's because the assumption itself is
wrong, or because a layer above hasn't filtered something out before
getting to this point.

--Jacob

Attachment Content-Type Size
regress-crash.diff.txt text/plain 729 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message kateriny bispo 2025-12-15 16:44:23 [PATCH] Add regression test for aggregate NULL behavior
Previous Message Robert Haas 2025-12-15 16:35:25 Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables