| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Sagar Shedge <sagar(dot)shedge92(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Extend postgres_fdw_get_connections to return remote backend pid |
| Date: | 2025-02-18 16:55:47 |
| Message-ID: | dc2f40af-7017-4f36-ad03-1078a2aac6ab@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025/02/18 23:44, Sagar Shedge wrote:
> Dear Hackers,
>
> I want to propose to extend existing postgres_fdw_get_connections
> functionality to return remote server backend pid.
> Using postgres_fdw extension, backend can establish connections to
> remote postgres servers. Recently we added functionality to get
> connection status which can help users to detect closed connections
> immediately. But currently there is no way to get a remote backend PID
> for these connections.
I assume you're planning to extend postgres_fdw_get_connections() to
also return the result of PQbackendPID(entry->conn).
However, the patch you attached doesn't seem to include that change.
Did you attach the wrong patch?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sagar Shedge | 2025-02-18 17:06:00 | Re: Extend postgres_fdw_get_connections to return remote backend pid |
| Previous Message | Tom Lane | 2025-02-18 16:54:45 | Re: BUG #18815: Logical replication worker Segmentation fault |