Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> No, it would take a protocol change to add such a thing out-of-line
> (that is, not as a LIMIT clause in the query text). The reason is that
> the planning is done at PARSE time, or at the latest BIND time. The
> row limit field in the EXECUTE message comes far too late to affect the
> query plan.
If planning is done at time of creation of the PreparedStatement
object (reminder: the example given above has no parameters), then the
setMaxRows() call will come too late whatever is the protocol change.
I mean: no protocol change can go back in time and "optimize" by not
doing useless work already done.
Thanks in advance for pointing out my mistake(s) here.
In response to
pgsql-jdbc by date
|Next:||From: Marc Herbert||Date: 2006-07-10 08:59:23|
|Subject: Re: Limit vs setMaxRows issue|
|Previous:||From: Giovanni M.||Date: 2006-07-10 01:48:27|
|Subject: Re: Dúvida|