From: | Rodrigo Ramírez Norambuena <decipher(dot)hk(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-08 01:30:41 |
Message-ID: | CAE9kuxPcvo-nAYv9fmMit5s=+=QfFSfYdZ_g4BY1yyY9ToVoJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 5, 2019 at 2:22 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> =?UTF-8?Q?Rodrigo_Ram=C3=ADrez_Norambuena?= <decipher(dot)hk(at)gmail(dot)com> writes:
> > 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.
>
> > 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.
>
> A couple of thoughts on this ---
> [...]
Hi Tom, about your concerns and feedback I send a new proposal of
patch related with the original idea.
Regards!
--
Rodrigo Ramírez Norambuena
http://www.rodrigoramirez.com/
Attachment | Content-Type | Size |
---|---|---|
0001-Add-to-the-conninfo-start-time-current-connection.patch | text/x-patch | 2.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2019-09-08 04:35:41 | Re: moonjelly vs tsearch |
Previous Message | Tom Lane | 2019-09-07 23:49:44 | Re: Change ereport level for QueuePartitionConstraintValidation |