From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jerry Brenner <jbrenner@guidewire.com>
cc: pgsql-performance@lists.postgresql.org
Subject: Re: Does Postgres have consistent identifiers (plan hash value) for
 explain plans?
In-reply-to: 
 <CACoKFYTVi5eq2Y2v5ni1X9KrDdv8HS_fPdU_rYm6Lr6p=0wjeQ@mail.gmail.com>
References: 
 <CACoKFYTVi5eq2Y2v5ni1X9KrDdv8HS_fPdU_rYm6Lr6p=0wjeQ@mail.gmail.com>
Comments: In-reply-to Jerry Brenner <jbrenner@guidewire.com>
	message dated "Mon, 04 Dec 2023 06:45:39 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <756531.1701701844.1@sss.pgh.pa.us>
Date: Mon, 04 Dec 2023 09:57:24 -0500
Message-ID: <756532.1701701844@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/756532.1701701844%40sss.pgh.pa.us>
Precedence: bulk

Jerry Brenner <jbrenner@guidewire.com> writes:
> Both Oracle and SQL Server have
> consistent hash values for query plans and that makes it easy to identify
> when there are multiple plans for the same query.  Does that concept exist
> in later releases of Postgres (and is the value stored in the json explain
> plan)?

No, there's no support currently for obtaining a hash value that's
associated with a plan rather than an input query tree.

			regards, tom lane