public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jerry Brenner <[email protected]>
To: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Is there a way to identify a plan generated by GECO?
Date: Fri, 18 Jul 2025 06:20:03 -0700
Message-ID: <CACoKFYQBVOmU3gRvmYhvBzSFTef02eMbn6ejxeR0sf5vSzbn4g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CACoKFYRSOZFA0m33BCDHBkget30sY71hMwH9peHvTKxcV6Ha4A@mail.gmail.com>
<[email protected]>
<CACoKFYQLSkeFwytFFaKXQBo3U79zTEoe5z6t24dTGEuKcpb9-Q@mail.gmail.com>
<[email protected]>
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
On Thu, Jul 17, 2025 at 8:10 PM Tom Lane <[email protected]> wrote:
> Jerry Brenner <[email protected]> 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
>
>
view thread (6+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Is there a way to identify a plan generated by GECO?
In-Reply-To: <CACoKFYQBVOmU3gRvmYhvBzSFTef02eMbn6ejxeR0sf5vSzbn4g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox