Re: psql large RSS (1.6GB)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Gavin Sherry <swm(at)alcove(dot)com(dot)au>
Cc: Dustin Sallings <dustin(at)spy(dot)net>, TTK Ciar <ttk2(at)hardpoint(dot)ciar(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: psql large RSS (1.6GB)
Date: 2004-11-01 14:04:44
Message-ID: 200411011404.iA1E4i407690@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2004-11-01 16:03:07 Re: psql large RSS (1.6GB)
Previous Message Gavin Sherry 2004-11-01 13:45:07 Re: psql large RSS (1.6GB)