Re: Re: Causeless CPU load waves in backend, on windows, 9.5.5 (EDB binary).

From: Nikolai Zhubr <n-a-zhubr(at)yandex(dot)ru>
To: undisclosed-recipients:;
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: Causeless CPU load waves in backend, on windows, 9.5.5 (EDB binary).
Date: 2017-02-14 21:06:11
Message-ID: 58A37143.6040709@yandex.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

14.02.2017 18:15, Rader, David:
[...]
> Try the libpq call from pg_isready. It does actually make a round trip
> to the postgres server and asks the server if it is ready to accept
> connections. So you are running the socket communication code of
> postgres and a small bit of "status" check but not any sql.

Indeed, such function is available. But essentially, this function is a
(kind of) combined login+logout, therefore it would not work for my
purpose. (Despite its name, it can not be used to perform some
communication "ping" within an established session, such thing simply
does not exist in the protocol, at least as of 9.5)

Regards,
Nikolai

>
> from mirror:
> https://github.com/postgres/postgres/blob/master/src/bin/scripts/pg_isready.c
>
> relevant call is PQping:
>
> rv = PQpingParams(keywords, values, 1);
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-02-14 21:38:50 Re: Bad planning data resulting in OOM killing of postgres
Previous Message John McKown 2017-02-14 20:58:38 Re: postgresql how to duplicate rows in result.