Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ucbUS-00Emi7-Jx
	for pgsql-performance@arkaria.postgresql.org; Fri, 18 Jul 2025 03:10:28 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1ucbUQ-0078BJ-Jz
	for pgsql-performance@arkaria.postgresql.org; Fri, 18 Jul 2025 03:10:27 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ucbUQ-0078B4-9P
	for pgsql-performance@lists.postgresql.org; Fri, 18 Jul 2025 03:10:26 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1ucbUO-008Mj5-1n
	for pgsql-performance@lists.postgresql.org;
	Fri, 18 Jul 2025 03:10:26 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 56I3AL3m1774626;
	Thu, 17 Jul 2025 23:10:21 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jerry Brenner <jbrenner@guidewire.com>
cc: pgsql-performance@lists.postgresql.org
Subject: Re: Is there a way to identify a plan generated by GECO?
In-reply-to: 
 <CACoKFYQLSkeFwytFFaKXQBo3U79zTEoe5z6t24dTGEuKcpb9-Q@mail.gmail.com>
References: 
 <CACoKFYRSOZFA0m33BCDHBkget30sY71hMwH9peHvTKxcV6Ha4A@mail.gmail.com>
 <1761501.1752803865@sss.pgh.pa.us>
 <CACoKFYQLSkeFwytFFaKXQBo3U79zTEoe5z6t24dTGEuKcpb9-Q@mail.gmail.com>
Comments: In-reply-to Jerry Brenner <jbrenner@guidewire.com>
	message dated "Thu, 17 Jul 2025 19:30:27 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1774624.1752808221.1@sss.pgh.pa.us>
Date: Thu, 17 Jul 2025 23:10:21 -0400
Message-ID: <1774625.1752808221@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/1774625.1752808221%40sss.pgh.pa.us>
Precedence: bulk

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