Re: [GENERAL] Re: Causeless CPU load waves in backend, on windows,9.5.5 (EDB binary). - Mailing list pgsql-general

From Nikolai Zhubr
Subject Re: [GENERAL] Re: Causeless CPU load waves in backend, on windows,9.5.5 (EDB binary).
Date
Msg-id 58A37143.6040709@yandex.ru
Whole thread Raw
In response to Re: [GENERAL] Re: Causeless CPU load waves in backend, on windows,9.5.5 (EDB binary).  ("Rader, David" <davidr@openscg.com>)
Responses Re: [GENERAL] Re: Causeless CPU load waves in backend, on windows,9.5.5 (EDB binary).  (Nikolai Zhubr <n-a-zhubr@yandex.ru>)
List 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);
>
>
>



pgsql-general by date:

Previous
From: John McKown
Date:
Subject: Re: [GENERAL] postgresql how to duplicate rows in result.
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Bad planning data resulting in OOM killing of postgres