| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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> |
| Subject: | Re: psql large RSS (1.6GB) |
| Date: | 2004-11-01 18:49:06 |
| Message-ID: | 200411011049.06770.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom,
> 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.
I think that TelegraphCQ incorporates this. However, I'm not sure whether
it's a portable component; it may be too tied in to their streaming query
engine. They have talked about porting their "background query" patch for
PSQL, though ...
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Nunes Melo | 2004-11-01 21:40:30 | Performance difference when using views |
| Previous Message | Anjan Dave | 2004-11-01 17:37:53 | shared_buffers and Shared Memory Segments |