pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Gavin Sherry <swm@alcove.com.au>
Cc: 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: Mon, 01 Nov 2004 11:03:07 -0500
Message-ID: <14203.1099324987@sss.pgh.pa.us> (raw)
In-Reply-To: <200411011404.iA1E4i407690@candle.pha.pa.us>
References: <200411011404.iA1E4i407690@candle.pha.pa.us>

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> No, I don't remember hearing this discussed and I don't think most
> people would want libpq spilling to disk by default.

Far more useful would be some sort of streaming API to let the
application process the rows as they arrive, or at least fetch the rows
in small batches (the V3 protocol supports the latter even without any
explicit use of a cursor).  I'm not sure if this can be bolted onto the
existing libpq framework reasonably, but that's the direction I'd prefer
to go in.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <14203.1099324987@sss.pgh.pa.us>
Permalink:  ../14203.1099324987@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14203.1099324987@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, swm@alcove.com.au, dustin@spy.net, ttk2@hardpoint.ciar.org
  Subject: Re: psql large RSS (1.6GB)
  In-Reply-To: <14203.1099324987@sss.pgh.pa.us>

* 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