Re: When manual analyze is needed

From: veem v <veema0000(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: When manual analyze is needed
Date: 2024-03-04 05:23:12
Message-ID: CAB+=1TVs1kGfCHpfeb5m02_eWaOXwBhnBD35fh8xrwcTa3SzVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Additionally if a query was working fine but suddenly takes a
suboptimal plan because of missing stats , do we have any hash value column
on any performance view associated with the queryid which we can refer to
see past vs current plans difference and identify such issues quickly and
fix it?
I am not seeing any such column in pg_stat_activity or pg_stat_statements
to hold hash value of the plan and also the query column is showing
"<insufficient privilege>" for many of the entries, why so?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michał Kłeczek 2024-03-04 06:46:33 Re: postgres_fdw aggregate pushdown for group by with expressions
Previous Message veem v 2024-03-04 04:46:35 Re: When manual analyze is needed