Re: Make EXPLAIN generate a generic plan for a parameterized query

From: Andres Freund <andres(at)anarazel(dot)de>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Make EXPLAIN generate a generic plan for a parameterized query
Date: 2022-12-06 18:17:08
Message-ID: 20221206181708.ict3to72wynzo3ao@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-10-29 10:35:26 +0200, Laurenz Albe wrote:
> On Tue, 2022-10-25 at 19:03 +0800, Julien Rouhaud wrote:
> > On Tue, Oct 25, 2022 at 11:08:27AM +0200, Laurenz Albe wrote:
> > > Here is a patch that
> > > implements it with an EXPLAIN option named GENERIC_PLAN.
> >
> > I only have a quick look at the patch for now.  Any reason why you don't rely
> > on the existing explain_filter() function for emitting stable output (without
> > having to remove the costs)?  It would also take care of checking that it works
> > in plpgsql.
>
> No, there is no principled reason I did it like that. Version 2 does it like
> you suggest.

This fails to build the docs:

https://cirrus-ci.com/task/5609301511766016

[17:47:01.064] ref/explain.sgml:179: parser error : Opening and ending tag mismatch: likeral line 179 and literal
[17:47:01.064] <likeral>ANALYZE</literal>, since a statement with unknown parameters
[17:47:01.064] ^

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-12-06 18:26:38 Re: [Proposal] Add foreign-server health checks infrastructure
Previous Message Corey Huinker 2022-12-06 18:16:59 Re: Error-safe user functions