Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Andrei Zubkov <zubkov(at)moonset(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Date: 2023-03-21 20:18:35
Message-ID: 4048041679429915@5z2o2ttyj7u3opu5.iva.yp-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

The documentation still describes the function pg_stat_statements_reset like this

> By default, this function can only be executed by superusers.

But unfortunately, this part was lost somewhere.

-- Don't want this to be available to non-superusers.
REVOKE ALL ON FUNCTION pg_stat_statements_reset(Oid, Oid, bigint, boolean) FROM PUBLIC;

should be added to the upgrade script

Also, shouldn't we first do:

/* First we have to remove them from the extension */
ALTER EXTENSION pg_stat_statements DROP VIEW ..
ALTER EXTENSION pg_stat_statements DROP FUNCTION ..

like in previous upgrade scripts?

> + Time at which min/max statistics gathering started for this
> + statement

I think it would be better to explicitly mention in the documentation all 4 fields for which minmax_stats_since displays the time.

regards, Sergei

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-03-21 20:45:58 Re: pgsql: Stop recommending auto-download of DTD files, and indeed disable
Previous Message Andres Freund 2023-03-21 20:11:46 Re: Save a few bytes in pg_attribute