From: | Vijaykumar Jain <vjain(at)opentable(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Profile a db connection time? |
Date: | 2019-10-11 16:43:12 |
Message-ID: | CAE7uO5jOgpBHRfhZqL10x9V3ipTokPsfcj-UdXX0O6Mvrs8E2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sorry if this is silly , but I have series of network outages and wanted to
understand if I can profile a psql connection to various parts of it
initialling a connection
Like when using hostname, resolving dns
the time to actually establish a db connection and then the time to parse
the query and run the query and time to return the results
I know a lot of the answers could be
Why not do a dns check before the connection,
run vacuum analyse to check only db time and do not return any row, and
then run with returning the rows and do a diff etc.
Am I asking something that makes sense?
Like google chrome does for page loading etc ?
--
Regards,
Vijay
From | Date | Subject | |
---|---|---|---|
Next Message | Julie Nishimura | 2019-10-11 17:23:05 | how can I get non-truncated version of running sql? |
Previous Message | Igal Sapir | 2019-10-11 16:10:52 | Re: Case Insensitive Comparison with Postgres 12 |