| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Gavin Sherry <swm(at)alcove(dot)com(dot)au>, 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 16:03:07 |
| Message-ID: | 14203.1099324987@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anjan Dave | 2004-11-01 17:37:53 | shared_buffers and Shared Memory Segments |
| Previous Message | Bruce Momjian | 2004-11-01 14:04:44 | Re: psql large RSS (1.6GB) |