Re: [HACKERS] Cached plans and statement generalization - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: [HACKERS] Cached plans and statement generalization
Date
Msg-id 83A439D3-ADEB-4F9D-8051-A4EC230F3C25@yesql.se
Whole thread Raw
In response to Re: [HACKERS] Cached plans and statement generalization  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 1 Mar 2020, at 20:26, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> In short, I really think we ought to reject this patch and move on.
> Maybe it could be resurrected sometime in the future when we have a
> better handle on when to cache plans and when not.
>
> If you want to press forward with it anyway, certainly the lack of
> any tests in this patch is another big objection.  Perhaps you
> could create a pgbench TAP script that exercises the logic.

Based on Tom's review, and that nothing has been submitted since, I've marked
this entry as returned with feedback.  Feel to open a new entry if you want to
address Tom's comments and take this further.

cheers ./daniel


pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Parallel copy
Next
From: michael@paquier.xyz
Date:
Subject: Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions?