From: | Jerry Brenner <jbrenner(at)guidewire(dot)com> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Does Postgres have consistent identifiers (plan hash value) for explain plans? |
Date: | 2023-12-04 14:45:39 |
Message-ID: | CACoKFYTVi5eq2Y2v5ni1X9KrDdv8HS_fPdU_rYm6Lr6p=0wjeQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
We are currently on Postgres 13.9 (and will be moving to later releases).
We are capturing json explain plans and storing them in a database table.
We can tell that there are different plans for some queries, but that's a
very labor intensive process - we'd rather do this using SQL and comparing
consistent hash values for the plans. 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)?
While we have a pretty good idea of how to manually generate a consistent
value, we don't want to reinvent the wheel. Is anyone aware of an existing
solution that can be called from SQL/jsonb?
Thanks,
Jerry
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-12-04 14:57:24 | Re: Does Postgres have consistent identifiers (plan hash value) for explain plans? |
Previous Message | Jeff Janes | 2023-12-04 03:15:27 | Re: Strange "actual time" in simple CTE |