Re: psql client memory usage

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 <mmoncure(at)gmail(dot)com> wrote:
>
> > On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane <tim(dot)kane(at)gmail(dot)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?

This is with PostgreSQL 9.2, see PQsetSingleRowMode:
http://www.postgresql.org/docs/9.2/static/libpq-single-row-mode.html

I do not expect psql will be adjusted to utilize the new API:
http://www.postgresql.org/message-id/CAEYkp92z2w3VBs4uxWPwub7k4hGW-vEPW_WNSui9R5T+cGpLYw@mail.gmail.com

-Ryan Kelly