From: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
---|---|
To: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
Subject: | Re: SCRAM pass-through authentication for postgres_fdw |
Date: | 2025-06-25 09:37:51 |
Message-ID: | ed0fb4f7e72950c19b6a9dfb2871b2a5@postgrespro.ru |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Matheus Alcantara писал(а) 2025-01-16 16:07:
> Em qua., 15 de jan. de 2025 às 14:03, Peter Eisentraut
> <peter(at)eisentraut(dot)org> escreveu:
>>
>> On 14.01.25 15:14, Matheus Alcantara wrote:
>> >> Attached is a fixup patch where I have tried to expand the documentation
>> >> a bit in an attempt to clarify how to use this. Maybe check that what I
>> >> wrote is correct.
>> >
>> > It looks good to me, it's much clearer now. Thanks.
>> >
>> > v4 attached with these fixes and also rebased with master.
>>
>> Committed, after pgindent and pgperltidy.
>
> Thanks!
Hi.
I've started to look at this feature and found an issue - MyProcPort can
be not set if connection is initiated
by some bgworker. (Internally we use one for statistics collection.) In
other places (for example, in be_gssapi_get_delegation())
there are checks that port is not NULL. Likely postgres_fdw and dblink
should do something similar.
--
Best regards,
Alexander Pyhalov,
Postgres Professional
Attachment | Content-Type | Size |
---|---|---|
0001-postgres_fdw-and-dblink-should-check-if-backend-has-.patch | text/x-diff | 4.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Shlok Kyal | 2025-06-25 09:40:04 | Re: Logical Replication of sequences |
Previous Message | Andrey Borodin | 2025-06-25 09:34:56 | Re: IPC/MultixactCreation on the Standby server |