postgres_fdw: use_scram_passthrough on user mapping is ignored when also set on server

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: postgres_fdw: use_scram_passthrough on user mapping is ignored when also set on server
Date: 2026-05-14 17:57:18
Message-ID: CAHGQGwEJ8rZjmbOvCicyr4vbuLio082bNTde0WNoSWaWr9wVcg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

use_scram_passthrough can be specified both on a foreign server and
on a user mapping. I found that when both are specified, currently
the server-level setting overrides the user mapping setting. Is this
precedence intentional?

That seems inconsistent with the usual expectation that foreign server
options act as shared defaults, while user mapping options provide
per-user overrides. If the same option is specified in both places,
I would expect the user mapping setting to take precedence. Thoughts?

If the current behavior is intentional, I'd like to document the precedence
when use_scram_passthrough is specified in both a foreign server and
a user mapping. Otherwise, I'd like to change postgres_fdw to prefer
the user mapping setting and update the documentation accordingly.

Regards,

--
Fujii Masao

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-05-14 17:58:29 Re: [PATCH] Fix for bug #19474: LIKE fails to match literal backslashes with nondeterministic collations
Previous Message Maxime Schoemans 2026-05-14 17:38:44 Set calcSumX2 = true in numeric_(poly_)deserialize