Re: [PATCH] Add features to pg_stat_statements

From: Katsuragi Yuta <btkatsuragiyu(at)oss(dot)nttdata(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Add features to pg_stat_statements
Date: 2020-09-23 08:13:36
Message-ID: 16a262a87492b4f4afc4c5010f8fa631@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-09-19 16:35, legrand legrand wrote:
> +1 !
>
> An other way is to log evictions, it provides informations about time
> and
> amount :
>
> for (i = 0; i < nvictims; i++)
> {
> hash_search(pgssp_hash, &entries[i]->key, HASH_REMOVE, NULL);
> }
>
> pfree(entries);
>
> /* trace when evicting entries, if appening too often this can slow
> queries
> ...
> * increasing pg_stat_sql_plans.max value could help */
> ereport(LOG,
> (errmsg("pg_stat_sql_plans evicting %d entries", nvictims),
> errhidecontext(true), errhidestmt(true)));
>
>
>
> --
> Sent from:
> https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html

Thank you for your comments!
In addition to providing a view that is like a summary of history,
logging might be a good choice.

Regards,
Katsuragi Yuta

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-09-23 08:17:00 Re: OpenSSL 3.0.0 compatibility
Previous Message Michael Paquier 2020-09-23 07:57:44 Re: Memory allocation abstraction in pgcrypto