From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
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 22:49:13 |
Message-ID: | 41155C69.2070407@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> 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?
Non-unnamed ones. Adding flag on the Parse message that says when to
plan the statement (or maybe on each Bind message even).
-O
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2004-08-07 23:28:44 | Re: [PATCHES] UNICODE characters above 0x10000 |
Previous Message | Alvaro Herrera | 2004-08-07 22:27:17 | Re: Regarding redo/undo files. |