From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Better Connection Statistics |
Date: | 2014-02-10 02:52:02 |
Message-ID: | CAB7nPqSVSpX+nCi_DQyzrT9U1TE1xawuCHqGc_qEbGY0NRwphg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
On Sun, Feb 9, 2014 at 4:52 AM, Greg Sabino Mullane <greg(at)turnstep(dot)com> wrote:
>> For instance, I want the number of transactions a specific connection has submitted.
>> The number of queries. Total amount of CPU time consumed, etc. So far as I know,
>> there is no module, statistic, or view that provides any of this.
>
> For the basic connection information, you could parse the Postgres logs, assuming
> you are being verbose enough to capture everything.
In this case, a log parser like pgbadger would help for sure.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tsubasa Sakamoto | 2014-02-10 04:51:38 | Re: client encoding that psql command sets |
Previous Message | Michael Paquier | 2014-02-10 02:49:15 | Re: WAL archive on slave |
From | Date | Subject | |
---|---|---|---|
Next Message | Glyn Astill | 2014-02-10 11:40:56 | Re: Better Connection Statistics |
Previous Message | Greg Sabino Mullane | 2014-02-08 19:52:39 | Re: Better Connection Statistics |