Re: Avoiding bad prepared-statement plans.
| От | Tom Lane |
|---|---|
| Тема | Re: Avoiding bad prepared-statement plans. |
| Дата | |
| Msg-id | 25921.1267330920@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Avoiding bad prepared-statement plans. (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Avoiding bad prepared-statement plans.
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Feb 26, 2010 at 7:03 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Wouldn't it be better if it just did the right thing automatically?
>>
>> The sort of heuristic I'm envisioning would essentially do "replan every
>> time" for some number of executions, and give up only if it noticed that
>> it wasn't getting anything better than the generic plan. �So you'd have
>> a fixed maximum overhead per session when the custom plan was useless,
>> and the Right Thing when it wasn't.
> Which is likely useless for my use case.
[ shrug... ] You'd better explain exactly why, if you want me to take
that objection seriously.
regards, tom lane
В списке pgsql-hackers по дате отправления: