First, you can probably offload a lot of the aggregations you are doing onto the database, which will likely do them faster. But that's neither here nor there..

If you are having trouble getting to the right data ranges fast enough, and your queries are almost always for small sub-ranges of 'timestamp' (which, I assume, is indexed) -- look into range partitioning. There is an explanation of how it works here: http://www.postgresql.org/docs/8.1/interactive/ddl-partitioning.html

Also, if you are versed in C, and PostgreSQL doesn't do the kind of aggregations you need out of the box, you should know that it does support user-defined aggregation functions: http://developer.postgresql.org/pgdocs/postgres/xaggr.html

Good luck

In reply to Re: PostgreSQL cursors with Perl. by dvryaboy
in thread PostgreSQL cursors with Perl. by atemerev

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.