Re: psql large RSS (1.6GB)

Bruce Momjian <pgman@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Gavin Sherry <swm@alcove.com.au>
Cc: Dustin Sallings <dustin@spy.net>, TTK Ciar <ttk2@hardpoint.ciar.org>, pgsql-performance@postgresql.org
Date: 2004-11-01T14:04:44Z
Lists: pgsql-performance
Gavin Sherry wrote:
> 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?

No, I don't remember hearing this discussed and I don't think most
people would want libpq spilling to disk by default.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073