| From: | Rodrigo Ramírez Norambuena <decipher(dot)hk(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Connection time for \conninfo |
| Date: | 2019-09-05 17:38:57 |
| Message-ID: | CAE9kuxMrQYbAfxB=8kNfkbLvfzuEGrNc2_7S-wk3kq+PDtiTRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 3, 2019 at 11:06 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> You can do basically the same thing by looking at
> pg_stat_activity.backend_start and compare it with the clock
> timestamp. Doing it at SQL level the way you want has also the
> advantage to offer you a modular format output.
Hi Michael,
Thanks you for paying attention, I appreciate this.
What are you say seams little trick to what I propose in this patch
because you'll need filter what is your connection, and if the
connection is through the connection pooler could be more.
The main goal this is only getting information from the client side
(psql) as frontend.
Regards!
--
Rodrigo Ramírez Norambuena
http://www.rodrigoramirez.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodrigo Ramírez Norambuena | 2019-09-05 17:40:02 | Re: [PATCH] Connection time for \conninfo |
| Previous Message | Tom Lane | 2019-09-05 17:32:04 | pgsql: Use data directory inode number, not port, to select SysV resour |