We just jdbc and bind variables, so we are using PreparedStatements.
plan_cache_mode is set to auto
So, it sounds like there could be plan caching. (I wasn't aware of that.)
Is there any kind of running counter in a system view that tracks the number of executions of cached plans?
We are capturing the plans via auto_explain and limited to the explain options available with that path. Is there anything in the plan that would tell us if the execution used a cached plan? (My manual explains does not use a prepare.)
Thanks, Jerry
Jerry Brenner <jbrenner@guidewire.com> writes:
> I don't have any background with the randomized search. Does the repeated
> pattern with the same plan being executed multiple times in a time range
> and then the plan changes, never to change back, match the expectation with
> the randomization?
[ shrug... ] Insufficient information. There could be some plan
caching going on that contributes to this effect, though.
regards, tom lane
