El día domingo, abril 25, 2021 a las 01:54:49p. m. +0200, Matthias Apitz escribió:
...
> # select * from pg_stat_activity where client_port = 52288;
>
> datid | datname | pid | leader_pid | usesysid | usename | application_name | client_addr |
client_hostname| client_port | backend_start | xact_start |
query_start | state_change | wait_event_type | wait_event | state |
backend_xid| backend_xmin | query | backend_type
>
--------+---------+-------+------------+----------+---------+---------------------------------+-------------+-----------------+-------------+---------------------------------+---------------------------------+---------------------------------+---------------------------------+-----------------+------------+---------------------+-------------+--------------+---------------------+----------------
> 951941 | sisis | 31894 | | 16384 | sisis | SunRise DBCALL V7.2 (pid=31864) | 127.0.0.1 |
| 52288 | 25.04.2021 10:57:15.922137 CEST | 25.04.2021 10:57:15.968081 CEST | 25.04.2021 10:57:16.051256
CEST| 25.04.2021 10:57:16.051273 CEST | Client | ClientRead | idle in transaction | 18314796 | 18314796
|fetch per_kette_seq | client backend
Having solved this issue, one last question: Is there any good way for a
C-written or ESQL/C-written client to get the local port number or even
the PID of the PostgreSQL server process on the other end of the
connection for logging/tracing purpose?
Thanks
matthias
--
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
¡Con Cuba no te metas! «» Don't mess with Cuba! «» Leg Dich nicht mit Kuba an!
http://www.cubadebate.cu/noticias/2020/12/25/en-video-con-cuba-no-te-metas/