Re: Reusing cached prepared statement slow after 5 executions

David Johnston <polobo@yahoo.com> 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