| From: | Jan de Visser <jan(at)de-visser(dot)net> |
|---|---|
| To: | basti <mailinglist(at)unix-solution(dot)de> |
| Cc: | postgre-gneral <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres connection Monitor |
| Date: | 2017-04-27 14:08:16 |
| Message-ID: | CAD7bhkGQJ-PR_o0Kix=ZGJ7Q4_7PpQNFL-+QqR+osrctjRgZYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 27, 2017 at 6:18 AM, basti <mailinglist(at)unix-solution(dot)de> wrote:
> Hallo, we have a Postgres database Server and around that there are 8
> clients get data from it.
>
> All servers are the the same datacenter i think (traceroute only 4-5 hops)
>
> Now we plan to move the server to an other hoster/datacenter.
>
> I have done simple test with ping and traceroute.
> Is there a way to monitor "traffic times" in postgres ?
> How long a query would take to be answered ?
You could write a tiny little C program which connects and sends a
PQping(), and measure that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Fougstedt | 2017-04-27 14:28:43 | Re: Query which "never" terminates |
| Previous Message | pinker | 2017-04-27 13:54:49 | Re: Query which "never" terminates |