| From: | Sagar Shedge <sagar(dot)shedge92(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Extend postgres_fdw_get_connections to return remote backend pid |
| Date: | 2025-02-18 17:06:00 |
| Message-ID: | CAPhYifGmL7OSajG1kbYHVbr642e23TQ=Y1y=rdB2K6mo0kmCQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fujii,
On Tue, Feb 18, 2025 at 10:25 PM Fujii Masao
<masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
> 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?
My bad!!
You are right. I was going through an old discussion and attached the
same old patch file.
Please refer to the patch file to return the remote backend pid.
--
Sagar Dilip Shedge,
SDE AWS
| Attachment | Content-Type | Size |
|---|---|---|
| v01_add_remote_backend_pid.patch | application/octet-stream | 8.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sébastien | 2025-02-18 17:13:06 | Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations |
| Previous Message | Fujii Masao | 2025-02-18 16:55:47 | Re: Extend postgres_fdw_get_connections to return remote backend pid |