Re: Extend postgres_fdw_get_connections to return remote backend pid

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-28 06:10:39
Message-ID: CAPhYifE3CR6YvuoEXGapB20W0qLEif4Oas6YgG0781TCMgS3UQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> For now, I think it makes sense to keep postgres_fdw_get_connections()
> aligned with the current implementation. Otherwise, explaining what
> remote_backend_pid = NULL means could be confusing, especially since
> pipeline mode isn't supported yet in postgres_fdw.

Make sense. I have created a patch according to the above suggestions.
Please review.

--
Sagar Dilip Shedge,
SDE AWS

Attachment Content-Type Size
v2-0001-Extend-postgres_fdw_get_connections-to-return-rem.patch application/octet-stream 12.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2025-02-28 06:19:32 Re: Disabling vacuum truncate for autovacuum
Previous Message Bertrand Drouvot 2025-02-28 05:54:44 Re: Log connection establishment timings