Re: Reusing cached prepared statement slow after 5 executions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: Rob Gansevles <rgansevles(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Reusing cached prepared statement slow after 5 executions
Date: 2011-06-26 15:11:44
Message-ID: 11490.1309101104@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2011-06-26 16:05:29 Re: An amusing MySQL weakness--not!
Previous Message David Johnston 2011-06-26 15:07:47 Re: Reusing cached prepared statement slow after 5 executions