Search Postgresql Archives

Re: Reusing cached prepared statement slow after 5 executions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I can confirm, when I call ps.setPrepareThreshold(1) the query is slow
immediately, so the plan must be different with the server prepared
statements.

Thanks,

Rob

On Sun, Jun 26, 2011 at 5:11 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> David Johnston <polobo@xxxxxxxxx> writes:
>> This is likely the case where the first few "prepared statements" are
>> not truly prepared.  Once you hit five the cache kicks in and computes
>> a generic query plan to cache.
>
> Not so much that as that JDBC decides that it should tell the backend to
> start using a prepared plan.  See the JDBC docs.
>
>                        regards, tom lane
>

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux