From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: parameter hints to the optimizer |
Date: | 2004-08-07 01:41:26 |
Message-ID: | 200408070141.i771fQp05906@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Oliver Jowett wrote:
> Merlin Moncure wrote:
>
> > Another way to deal with the problem is to defer plan generation until
> > the first plan execution and use the parameters from that execution.
>
> When talking the V3 protocol, 7.5 defers plan generation for the unnamed
> statement until parameters are received in the Bind message (which is
> essentially the same as what you describe). There was some discussion at
> the time about making it more flexible so you could apply it to arbitary
> statements, but that needed a protocol change so it didn't happen.
What do you mean about arbitrary statements? Non-prepared ones, or
non-unnamed ones?
I am trying to figure out what TODO item needs to be added.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-08-07 01:50:01 | Re: [PATCHES] [BUGS] casting strings to multidimensional arrays yields |
Previous Message | Bruce Momjian | 2004-08-07 01:04:34 | Re: regexp_replace |