From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | 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-10-29 08:35:26 |
Message-ID: | 5ebe9c28d740a4bc4ad627c281d6a2cbfc684ffc.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
0001-Add-EXPLAIN-option-GENERIC_PLAN.v2.patch | text/x-patch | 8.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | jacktby@gmail.com | 2022-10-29 09:25:32 | access method xxx does not exist |
Previous Message | Bharath Rupireddy | 2022-10-29 06:24:02 | Re: Use pg_pwritev_with_retry() instead of write() in dir_open_for_write() to avoid partial writes? |