Re: Extend postgres_fdw_get_connections to return remote backend pid

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Sagar Shedge <sagar(dot)shedge92(at)gmail(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 12:02:43
Message-ID: 952d26b6-d84b-4ac3-8d48-6cbcae094970@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025/02/28 15:10, Sagar Shedge wrote:
>> 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.

Thanks for updating the patch!

I made a few cosmetic adjustments and attached the revised version.
Unless there are any objections, I plan to commit this.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

Attachment Content-Type Size
v3-0001-postgres_fdw-Extend-postgres_fdw_get_connections-.patch text/plain 12.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yuki Seino 2025-02-28 12:08:01 Re: Add “FOR UPDATE NOWAIT” lock details to the log.
Previous Message Ashutosh Bapat 2025-02-28 12:01:41 Re: Changing shared_buffers without restart