Re: Speeding up a query.

От: Alberto Dalmaso
Тема: Re: Speeding up a query.
Дата: ,
Msg-id: 1245231239.5027.113.camel@dalmaso-opensuse.cl
(см: обсуждение, исходный текст)
Ответ на: Speeding up a query.  ("Hartman, Matthew")
Ответы: Re: Speeding up a query.  ("Kevin Grittner")
Re: Speeding up a query.  (Tom Lane)
Список: pgsql-performance

Скрыть дерево обсуждения

Speeding up a query.  ("Hartman, Matthew", )
       Re: Speeding up a query.  (Anthony Presley, )
        Re: Speeding up a query.  ("Hartman, Matthew", )
       Re: Speeding up a query.  ("Albe Laurenz", )
        Re: Speeding up a query.  (Grzegorz Jaśkiewicz, )
       Re: Speeding up a query.  (Alberto Dalmaso, )
        Re: Speeding up a query.  ("Kevin Grittner", )
        Re: Speeding up a query.  (Tom Lane, )
       Re: Speeding up a query.  (Merlin Moncure, )
        Re: Speeding up a query.  ("Hartman, Matthew", )
       Re: Speeding up a query.  ("Hartman, Matthew", )
       Re: Speeding up a query.  (Simon Riggs, )
        Re: Speeding up a query.  ("Hartman, Matthew", )

yes, I have to make that because the data on the table need to be
pivoted so it is joined many times with different filter on the column
that describe the meaning of the column called numeric_value I'm going
to show.
That could be very ineffective, event because that table contains
something like 25000000 rows...
There are two tables in this condition (as you can se in the explain)
and both are the table with the higher number of rows in the database.
But I don's see any other choice to obtain that information.

P.S.: i'm trying with all enable_* to on and pumping to higher values
from_collapse_limit and join_collapse_limit that I've put to 30.
The result is that the query, after an hour of work, goes out of memory
(SQL State 53200)...



В списке pgsql-performance по дате сообщения:

От: "Hartman, Matthew"
Дата:
Сообщение: Re: Speeding up a query.
От: "Kevin Grittner"
Дата:
Сообщение: Re: performance with query