| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | amandeep singh <singh_a(at)live(dot)in> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Unknown in place of application name |
| Date: | 2017-08-07 14:31:14 |
| Message-ID: | 23595.1502116274@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
amandeep singh <singh_a(at)live(dot)in> writes:
> After enabling I have checked the log and found that all new connections are showing unknown for application name however it is showing application name in disconnection. Same is tested with multiple applications and getting same result.
> 2017-08-07 18:55:44 IST [[unknown]] LOG: connection received: host=[local]
> 2017-08-07 18:55:48 IST [[unknown]] LOG: connection received: host=[local]
> 2017-08-07 18:55:48 IST [[unknown]] LOG: connection authorized: user=postgres database=postgres
> 2017-08-07 18:55:54 IST [psql.bin] LOG: disconnection: session time: 0:00:06.004 user=postgres database=postgres host=[local]
This is unsurprising: the connection received/authorized messages come
out before absorbing any parameters (such as application_name) from
the connection request packet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sathesh S | 2017-08-10 17:56:32 | Performance impact for enabling Log_disconnections |
| Previous Message | amandeep singh | 2017-08-07 13:41:07 | Unknown in place of application name |