Re: Cursor-based results: bafflingly slow - Mailing list pgsql-jdbc

From Robin Houston
Subject Re: Cursor-based results: bafflingly slow
Date
Msg-id 1b795e7b0907030738v67964f36ic4bbbf39ace0e5af@mail.gmail.com
Whole thread Raw
In response to Re: Cursor-based results: bafflingly slow  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
2009/7/3 Tom Lane <tgl@sss.pgh.pa.us>
You need to use a cursor for that.  The problem with the fetchsize
mechanism is that it doesn't give the planner any clue that the user
might not intend to fetch the whole result, or might prefer low startup
cost to low total cost anyway.

Thank you very much (and Oliver too). That's what I needed to know. I'll change my code to use explicit cursors.

Robin

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cursor-based results: bafflingly slow
Next
From: Jamie D
Date:
Subject: setQueryTimeout