Re: Command statistics system (cmdstats) - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: Command statistics system (cmdstats)
Date
Msg-id 8FF6A881-0BB5-44CE-A833-E87060234EAC@enterprisedb.com
Whole thread Raw
In response to Command statistics system (cmdstats)  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: Command statistics system (cmdstats)
List pgsql-hackers
> On Mar 4, 2020, at 7:43 PM, Mark Dilger <mark.dilger@enterprisedb.com> wrote:
>
> Hackers,
>
> as mentioned in [1], I have created an implementation of command counter statistics very similar in purpose to the
onealready pending in the commitfest going by the name "pg_stat_sql".  I don't really care if this implementation is
seenas building on that one or as separate, but I was worried about hijacking that thread, so I'm starting this thead.
Thereare elements of this patch that borrowed from that one, so if this is accepted, authorship should reflect that. 
>
> See the work by Haribabu Kommi (haribabu) at https://commitfest.postgresql.org/27/790/
>
> The two main differences are that
>
> (1) This implementation is based on commandtags as enums, not strings and
> (2) This implementation uses techniques to reduce lock contention
>
> I think (2) is the more important part.
>
> [1] https://www.postgresql.org/message-id/28F46159-3764-421B-904B-004DEA339310%40enterprisedb.com
>
> <v1-0001-Implementing-the-cmdstats-subsystem.patch>
> —

Rebased patch against master caa3c4242cf86322e2ed0c86199e6462a2c41565.



—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company




Attachment

pgsql-hackers by date:

Previous
From: Martín Marqués
Date:
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view
Next
From: Mark Dilger
Date:
Subject: Re: Command statistics system (cmdstats)