From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: libpq - lack of support to set the fetch size |
Date: | 2014-03-10 09:48:00 |
Message-ID: | 531D8A50.2070603@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/9/2014 6:43 AM, matshyeq wrote:
> Hello,
>
> I've found an issue when tried to implement fetching rows from big
> table (2mln rows) in my app.
> Basically I don't find an elegant and easy way (other than always use
> cursors) to limit the number of rows returned.
> This causes my application to break due to the excessive memory
> consumption.
>
> I'm using Perl and DBD::Pg library but contacted maintainer who
> actually pointed out this is an issue that goes much deeper (libpq):
>
> "Unfortunately, this is a limitation in the underlying driver (libpq)
> rather than DBD::Pg itself. There have been talks over the years of
> supporting this, but nothing concrete yet. Your best bet would be to
> ask about this on the Postgres lists"
>
in addition to what the others suggested, you can use a CURSOR to read
through results in arbitrary sized blocks.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
From | Date | Subject | |
---|---|---|---|
Next Message | matshyeq | 2014-03-10 11:51:39 | Re: libpq - lack of support to set the fetch size |
Previous Message | Albe Laurenz | 2014-03-10 09:42:21 | Re: libpq - lack of support to set the fetch size |