David Rysdam <drysdam@xxxxxxxxxx> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
