Re: join to view over custom aggregate seems like it should be faster

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: join to view over custom aggregate seems like it should be faster
Дата
Msg-id b42b73150704091436g7fd1f903q1209218fc5eee88d@mail.gmail.com
обсуждение исходный текст
Ответ на Re: join to view over custom aggregate seems like it should be faster  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: join to view over custom aggregate seems like it should be faster  ("Merlin Moncure" <mmoncure@gmail.com>)
Список pgsql-performance
On 4/9/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Merlin Moncure" <mmoncure@gmail.com> writes:
> > I have an odd performance issue on 8.2 that I'd thought I'd document
> > here.  I have a workaround, but I'm if there is something that I'm not
> > seeing.
>
> It's hard to comment on this without seeing the full details of the view
> and tables.  I'm wondering where the SubPlans are coming from, for instance.

ah, it looks like the aggregate is being re-expanded for each field
returned by the aggregate.  I notice this for non-trivial record
returning functions also.  standard m.o. is to push into a subquery
and expand afterwords.

merlin

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

Предыдущее
От: "Merlin Moncure"
Дата:
Сообщение: Re: join to view over custom aggregate seems like it should be faster
Следующее
От: Tom Lane
Дата:
Сообщение: Re: how to efficiently update tuple in many-to-many relationship?