Re: Does Postgres have consistent identifiers (plan hash value) for explain plans?
От
Michael Paquier
Тема
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans?
Дата
Msg-id
ZW6TdlN7Im7h2KCd@paquier.xyz
Ответ на
Список
Дерево обсуждения
Does Postgres have consistent identifiers (plan hash value) for explain plans? Jerry Brenner <jbrenner@guidewire.com>
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? Tom Lane <tgl@sss.pgh.pa.us>
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? Michael Paquier <michael@paquier.xyz>
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? Tom Lane <tgl@sss.pgh.pa.us>
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? Jerry Brenner <jbrenner@guidewire.com>
Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? Julien Rouhaud <rjuju123@gmail.com>
On Mon, Dec 04, 2023 at 09:57:24AM -0500, Tom Lane wrote: > Jerry Brenner 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. PlannerGlobal includes a no_query_jumble that gets inherited by all its lower-level nodes, so adding support for hashes compiled from these node structures would not be that complicated. My point is that the basic infrastructure is in place in the tree to be able to do that, and it should not be a problem to even publish the compiled hashes in EXPLAIN outputs, behind an option of course. -- Michael
В списке pgsql-performance по дате отправления
От: Julien Rouhaud
Дата:
От: Tom Lane
Дата: