On Sep 6, 2013, at 6:56 AM, Merlin Moncure wrote:
> On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane wrote:
>> Ahh. All these years (albeit sporadic), I never knew about FETCH_COUNT.
>> That makes sense. Thanks muchly.
>
> Not your fault: FETCH_COUNT is a hack IMO. The real issue was that
> libpq (un
On Mon, Sep 09/09/13, 2013 at 01:56:33PM -0700, Alan Nilsson wrote:
>
> On Sep 6, 2013, at 6:56 AM, Merlin Moncure wrote:
>
> > On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane wrote:
> >> Ahh. All these years (albeit sporadic), I never knew about FETCH_COUNT.
> >> That makes sense. Thanks muchly.
> >
On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane wrote:
> Ahh. All these years (albeit sporadic), I never knew about FETCH_COUNT.
> That makes sense. Thanks muchly.
Not your fault: FETCH_COUNT is a hack IMO. The real issue was that
libpq (until recently) forced the entire result into memory before it
wa
Ahh. All these years (albeit sporadic), I never knew about FETCH_COUNT.
That makes sense. Thanks muchly.
On 06/09/2013 14:11, "Suzuki Hironobu" wrote:
>(13/09/06 21:06), Tim Kane wrote:
>> Hi all,
>>
>> I have a fairly simple query, running on a particularly large table.
>>For
>> illustration
(13/09/06 21:06), Tim Kane wrote:
Hi all,
I have a fairly simple query, running on a particularly large table. For
illustration:
echo "select * from really_big_table;" | psql my_database > /dev/null
When I monitor the memory usage of the psql session, it continually grows.
In fact, for this
Tim Kane wrote:
> I have a fairly simple query, running on a particularly large table. For
> illustration:
>
> echo "select * from really_big_table;" | psql my_database > /dev/null
See psql's FETCH_COUNT. From the manpage:
FETCH_COUNT
If this variable is set t
Hi all,
I have a fairly simple query, running on a particularly large table. For
illustration:
echo "select * from really_big_table;" | psql my_database > /dev/null
When I monitor the memory usage of the psql session, it continually grows.
In fact, for this particularly large table it grows
