David Johnston <polobo(at)yahoo(dot)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
In response to
pgsql-general by date
|Next:||From: Stephen Frost||Date: 2011-06-26 16:05:29|
|Subject: Re: An amusing MySQL weakness--not!|
|Previous:||From: David Johnston||Date: 2011-06-26 15:07:47|
|Subject: Re: Reusing cached prepared statement slow after 5 executions|