| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, andrey(dot)chudnovskiy(at)microsoft(dot)com |
| Subject: | Re: Log connection establishment timings |
| Date: | 2024-12-16 23:26:20 |
| Message-ID: | CAGECzQQp0kzsgCdkMdFEiqmnVCc8YGKEVSRcqVPyMbRJVb6B_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 16 Dec 2024 at 22:00, Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
> Users wishing to debug slow connection establishment have little
> visibility into which steps take the most time. We don't expose any
> stats and none of the logging includes durations.
Two thoughts:
1. Would it make sense to also expose these timings in some pg_stat_xyz view?
2. As a user I'd be curious to know how much of the time is spent on
the network/client vs inside postgres. For example for the scram/sasl
handshake, how much of the authentication_time is spent waiting on the
first "read" after the server has called sendAuthRequest.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2024-12-16 23:43:32 | Re: WARNING: missing lock on database "postgres" (OID 5) @ TID (0,4) |
| Previous Message | Robert Haas | 2024-12-16 23:23:45 | Re: FileFallocate misbehaving on XFS |