Re: Avoiding bad prepared-statement plans.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Avoiding bad prepared-statement plans.
Дата
Msg-id 1005.1267207904@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Avoiding bad prepared-statement plans.  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Feb 26, 2010 at 10:07 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think this is basically a planner problem and should be fixed in the
>> planner, not by expecting users to make significant changes in
>> application logic in order to create an indirect effect.

> I would agree if I thought that were possible, but I'm skeptical about
> your proposed solution.

Fair enough --- maybe it will work well enough, or maybe it won't.
But the same can be said of every other proposal that's been made.
I'm in favor of trying the simpler approaches first.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: ecpg tests broken by pgindent run
Следующее
От: Tom Lane
Дата:
Сообщение: Re: ProcSignalSlot vs. PGPROC