Re: New SQL counter statistics view (pg_stat_sql) - Mailing list pgsql-hackers

From neha khatri
Subject Re: New SQL counter statistics view (pg_stat_sql)
Date
Msg-id CAFO0U+-pS2cSJiaqJ8vkGGJka8MxLnKHemwgQUCD44AW+uVn1g@mail.gmail.com
Whole thread Raw
In response to Re: New SQL counter statistics view (pg_stat_sql)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New SQL counter statistics view (pg_stat_sql)  (Gavin Flower <GavinFlower@archidevsys.co.nz>)
List pgsql-hackers
>Andres Freund <andres@anarazel.de> writes:
>> On 2016-08-22 13:54:43 -0400, Robert Haas wrote:
>> On Sat, Aug 20, 2016 at 11:17 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> I'm inclined to suggest you forget this approach and propose a single
>>>> counter for "SQL commands executed", which avoids all of the above
>>>> definitional problems.  People who need more detail than that are
>>>> probably best advised to look to contrib/pg_stat_statements, anyway.

>>> I disagree.  I think SQL commands executed, lumping absolutely
>>> everything together, really isn't much use.

>> I'm inclined to agree. I think that's a quite useful stat when looking
>> at an installation one previously didn't have a lot of interaction with.

>Well, let's at least have an "other" category so you can add up the
>counters and get a meaningful total.

How would that meaningful total might help a user. What can a user might analyse with the counter in 'other' category.


Neha

pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)
Next
From: Michael Paquier
Date:
Subject: Re: pg_dump with tables created in schemas created by extensions