Re: SCRAM pass-through authentication for postgres_fdw
Alexander Pyhalov <a.pyhalov@postgrespro.ru>
From: Alexander Pyhalov <a.pyhalov@postgrespro.ru>
To: Matheus Alcantara <matheusssilv97@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, PostgreSQL Hackers
<pgsql-hackers@lists.postgresql.org>, Jacob Champion
<jacob.champion@enterprisedb.com>
Date: 2025-06-25T09:37:51Z
Lists: pgsql-hackers
Attachments
Matheus Alcantara писал(а) 2025-01-16 16:07: > Em qua., 15 de jan. de 2025 às 14:03, Peter Eisentraut > <peter@eisentraut.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