Depending on how many columns in your result set, and how complicated your query, 3,000,000 records shouldn't be that big of a deal. You really should show us your perl code, your SQL, and your database schema as you could be doing something strange that's eating your memory and we would never know it. For instance, if you load the entire result set into a perl array, that might not be the best thing for memory consumption. Another for instance, if you're doing a 5 table join on all columns but are only using a few columns from the result set, that too might not be the best thing.

duff

In reply to Re: What are effective methods for retriving many number of rows from postgreSQL tables using perl DBI? by duff
in thread What are effective methods for retriving many number of rows from postgreSQL tables using perl DBI? by targetsmart

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.