First of all the more method calls for bind_columns shouldn't be a problem.

You should generally use placeholders and bind parameters. When you call prepare, a stored procedure is created internally and reused each time you call execute on that handle - which is more efficient than calling do($statement) mutlitple times.

You should just try a query with limit and offset to retrieve the data patch by patch, and try a query that returns them all and transfer them row by with selectrow_arrayref or selectrow_array. Then benchmark to find out which one is faster.

Perl 6 in German

In reply to Re: What are effective methods for retriving many number of rows from postgreSQL tables using perl DBI? by moritz
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.