| From: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com> |
|---|---|
| To: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
| 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 11:36:46 |
| Message-ID: | CAFY6G8eDU_Wn++bpFRXOL-MQHe6Bn2XJx9TypFLDQ0BxMJkxKQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, thanks for testing and reporting the issue!
On 25/06/25 11:37, Alexander Pyhalov wrote:
> 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.
>
In this case the bgworker is used to collect statistics for the fdw
tables? If that's the case, since we don't have the MyProcPort and the
scram keys, will it use the user and password configured on user mapping
properties? If that's also the case I think that we may have a problem
because the goal of this feature is to avoid storing the password on
user mapping.
Do you have steps to reproduce the issue?
--
Matheus Alcantara
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2025-06-25 11:39:08 | Re: INSERT ... ON CONFLICT DO SELECT [FOR ...] take 2 |
| Previous Message | Amit Kapila | 2025-06-25 11:26:41 | Re: Conflict detection for update_deleted in logical replication |