Search Postgresql Archives

Re: psql client memory usage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> wrote:
> 
> > On Fri, Sep 6, 2013 at 8:19 AM, Tim Kane <tim.kane@xxxxxxxxx> 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@xxxxxxxxxxxxxx

-Ryan Kelly


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux