Re: psql client memory usage - Mailing list pgsql-general

From Alan Nilsson
Subject Re: psql client memory usage
Date
Msg-id 408F5BB4-2CEC-4857-B8BB-01C84648F3A2@apple.com
Whole thread Raw
In response to Re: psql client memory usage  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: psql client memory usage  (Ryan Kelly <rpkelly22@gmail.com>)
List pgsql-general
On Sep 6, 2013, at 6:56 AM, Merlin Moncure <mmoncure@gmail.com> wrote:

> On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane <tim.kane@gmail.com> 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
> was returned to the caller.  We can now in libpq (thanks Marko) that
> allows process rows as they come in.  I expect soon psql will be
> adjusted to utilize that new API (although exactly how is unclear);

what version did/does this come into effect?

alan




pgsql-general by date:

Previous
From: patrick keshishian
Date:
Subject: Re: Call for design: PostgreSQL mugs
Next
From: Ryan Kelly
Date:
Subject: Re: psql client memory usage