Re: psql large RSS (1.6GB) - Mailing list pgsql-performance

From Gavin Sherry
Subject Re: psql large RSS (1.6GB)
Date
Msg-id Pine.LNX.4.58.0411020042050.5412@linuxworld.com.au
Whole thread Raw
In response to Re: psql large RSS (1.6GB)  (Dustin Sallings <dustin@spy.net>)
Responses Re: psql large RSS (1.6GB)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-performance
On Sat, 30 Oct 2004, Dustin Sallings wrote:

> >   If the solution is to just write a little client that uses perl
> > DBI to fetch rows one at a time and write them out, that's doable,
> > but it would be nice if psql could be made to "just work" without
> > the monster RSS.
>
>     It wouldn't make a difference unless that driver implements the
> underlying protocol on its own.

Even though we can tell people to make use of cursors, it seems that
memory usage for large result sets should be addressed. A quick search of
the archives does not reveal any discussion about having libpq spill to
disk if a result set reaches some threshold. Has this been canvassed in
the past?

Thanks,

Gavin

pgsql-performance by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: Thanks Chariot Solutions
Next
From: Bruce Momjian
Date:
Subject: Re: psql large RSS (1.6GB)