| From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Limit vs setMaxRows issue |
| Date: | 2006-07-12 10:59:28 |
| Message-ID: | 44B4D610.9010105@logix-tt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi, Marc,
Marc Herbert wrote:
> Even if you delay the parsing on the first execution in order to wait
> for any helpful but late .setMaxRows(), then later .setMaxRows() on
> the next re-executions will come after parsing anyway. Unless you
> kinda re-parse every time...
Only when setMaxRows() actually changes.
And theoretically, only re-planning is required, not re-parsing, but
currently the server does not allow clients to control those steps
independently.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lucas Sousa | 2006-07-12 11:45:01 | Re: executeQuery Locked |
| Previous Message | Marc Herbert | 2006-07-12 10:22:51 | Re: Limit vs setMaxRows issue |