From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | ashok raj <ashokexplorer(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: AutoExplain printing sql_hash and plan_hash |
Date: | 2023-02-24 05:04:56 |
Message-ID: | CAOBaU_apXZAFpeKRTzWv=V=19ejJhJm83wYSKR8cmSs6Nf-fFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
hi
Le ven. 24 févr. 2023 à 12:45, ashok raj <ashokexplorer(at)gmail(dot)com> a écrit :
> Hello Team,
>
> We are printing the Explain Analyze plan for the slow queries using
> auto_explain extension. To do more analysis, I think it would be nice to
> print sql_hash and plan_hash along with the explain plan.
>
> Currently from the docs I don't see a way todo this.
>
you're right it's not currently possible, but this feature was added last
month and will be available with pg16. note that I'm only talking about the
query_id (which should be what you call query hash) as there's no plan hash
in postgres itself. there are exceptions for that like pg_store_plans but
those can't add information to auto_explain output.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-02-24 13:00:12 | Re: PostgreSQL, change encoding preserving data |
Previous Message | ashok raj | 2023-02-24 04:45:17 | AutoExplain printing sql_hash and plan_hash |