From: | neha khatri <nehakhatri5(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New SQL counter statistics view (pg_stat_sql) |
Date: | 2016-08-24 00:02:26 |
Message-ID: | CAFO0U+-pS2cSJiaqJ8vkGGJka8MxLnKHemwgQUCD44AW+uVn1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>Andres Freund <andres(at)anarazel(dot)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(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-08-24 00:07:18 | Re: pg_dump with tables created in schemas created by extensions |
Previous Message | Greg Stark | 2016-08-23 23:50:20 | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |