Re: Cursor-based results: bafflingly slow

From: Robin Houston <robin(dot)houston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Cursor-based results: bafflingly slow
Date: 2009-07-03 14:38:11
Message-ID: 1b795e7b0907030738v67964f36ic4bbbf39ace0e5af@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

2009/7/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Jamie D 2009-07-06 00:55:27 setQueryTimeout
Previous Message Tom Lane 2009-07-03 14:24:35 Re: Cursor-based results: bafflingly slow