From: Gavin Sherry <swm@alcove.com.au>
To: Dustin Sallings <dustin@spy.net>
Cc: TTK Ciar <ttk2@hardpoint.ciar.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: psql large RSS (1.6GB)
Date: Tue, 2 Nov 2004 00:45:07 +1100 (EST)
Message-ID: <Pine.LNX.4.58.0411020042050.5412@linuxworld.com.au> (raw)
In-Reply-To: <8132EBC8-2B02-11D9-A2DE-000A957659CC@spy.net>
References: <20041027075748.GA8355@hardpoint.ciar.org>
<8132EBC8-2B02-11D9-A2DE-000A957659CC@spy.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swm@alcove.com.au, dustin@spy.net, ttk2@hardpoint.ciar.org
Subject: Re: psql large RSS (1.6GB)
In-Reply-To: <Pine.LNX.4.58.0411020042050.5412@linuxworld.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox