| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rysdam <drysdam(at)ll(dot)mit(dot)edu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Very slow queries on 8.1 |
| Date: | 2005-11-17 16:46:45 |
| Message-ID: | 27047.1132246005@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Rysdam <drysdam(at)ll(dot)mit(dot)edu> writes:
> Right, it's about 100k rows and it is through libpq (pgadmin in this
> case, but my app uses libpq from pgtcl). Is there a way to tell libpq
> to not do what it "likes" and do what I need instead?
The only way ATM is to declare a cursor on the query and then FETCH
whatever amount seems reasonable at a time.
There is support in the on-the-wire protocol for partial fetches from
ordinary queries (ie, without the notational overhead of creating a
cursor). libpq doesn't expose that at the moment. There's a thread
right now in pgsql-interfaces about adding such a feature to libpq ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-11-17 16:48:31 | Re: Very slow queries on 8.1 |
| Previous Message | Mott Leroy | 2005-11-17 16:43:24 | Re: Incomplete Startup Packet |