Re: SELECT AND AGG huge tables - Mailing list pgsql-performance

From Ants Aasma
Subject Re: SELECT AND AGG huge tables
Date
Msg-id CA+CSw_uHEriZmX-ye31+HZfAR56hoH4qS5TC2U8UGAEY_PXwMA@mail.gmail.com
Whole thread Raw
In response to Re: SELECT AND AGG huge tables  (houmanb <houman@gmx.at>)
List pgsql-performance
On Wed, Oct 17, 2012 at 2:24 PM, houmanb <houman@gmx.at> wrote:
> Hi all,
> Thanks for your advice and the link about posting my question in an
> appropriate form.
> Here are the info. I thank all of you in advance.

Can you run the EXPLAIN once more with EXPLAIN (ANALYZE, BUFFERS,
TIMING OFF). Given the number of rows processed by the query, the
detailed per node timing overhead might be a considerable factor here.

What happened to the "WHERE T.creation_date=$SOME_DATE" part of the
query. These examples go through the whole table. The plans shown are
about as fast as it gets. Summarizing 5GB of data will never be fast.
If you need that information quickly, you'll need to actively maintain
the aggregate values via triggers.

Regards,
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de


pgsql-performance by date:

Previous
From: delongboy
Date:
Subject: How to upgrade from 9.1 to 9.2 with replication?
Next
From: Tom Lane
Date:
Subject: Re: Recursive query gets slower when adding an index