Re: Prepared statements and generic plans

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prepared statements and generic plans
Date: 2016-06-04 02:20:35
Message-ID: 20160604022035.GA11505@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 3, 2016 at 08:27:38AM -0400, David G. Johnston wrote:
> ​This goes back to Bruce's motivation but as long as it goes into the internals
> section I have no problem adding material that someone felt was worth their

OK, updated version attached. I added "potential" to the first
paragraph, and added "estimated cost" to the later part, fixed the
"cheaper than", and clarified that we add the plan time cost to the
non-generic plan, which is how it can be cheaper than the generic plan.
I also moved the "Once a generic plan is chosen" line.

Yeah, that's a lot of changes, but they all improved the text. Thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

Attachment Content-Type Size
prepare.diff text/x-diff 4.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2016-06-04 02:25:52 Re: Reviewing freeze map code
Previous Message Christophe Pettus 2016-06-04 02:10:44 HashAggregate row estimate = 200