Re: parameter hints to the optimizer - Mailing list pgsql-hackers

From Oliver Jowett
Subject Re: parameter hints to the optimizer
Date
Msg-id 41155C69.2070407@opencloud.com
Whole thread Raw
In response to Re: parameter hints to the optimizer  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: parameter hints to the optimizer  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Regarding redo/undo files.
Next
From: "John Hansen"
Date:
Subject: Re: [PATCHES] UNICODE characters above 0x10000