postgres-github.git / summary / log / commit / refs

commit    97f6fc10fff0e42d08d78ce7f2a5b116e7f8d9b2
Author:   Fujii Masao <fujii@postgresql.org>
Date:     Mon May 25 15:46:31 2026 +0000

    postgres_fdw: Give user mapping precedence for use_scram_passthrough
    
    Previously, when use_scram_passthrough was specified on both a foreign server
    and a user mapping, the server-level setting took precedence over the
    user-mapping setting. This was inconsistent with the usual semantics of
    postgres_fdw options, where foreign server options provide shared defaults
    and user mapping options override them on a per-user basis.
    
    This commit updates postgres_fdw so that the user-mapping setting takes
    precedence when use_scram_passthrough is specified in both places. This
    matches the behavior of other connection options such as sslcert and sslkey.
    
    Backpatch to v18, where use_scram_passthrough was introduced. In v18,
    this only affects limited configurations that specify conflicting values
    at both the foreign server and user-mapping levels. In such cases, users
    would naturally expect the user-mapping setting to override the server-level
    setting, so changing the behavior should be minimally disruptive.
    Also keeping v18 as the only branch with different semantics for
    use_scram_passthrough would be unnecessarily confusing, so backpatch
    this fix to v18.
    
    Author: Matheus Alcantara <matheusssilv97@gmail.com>
    Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
    Discussion: https://postgr.es/m/CAHGQGwEJ8rZjmbOvCicyr4vbuLio082bNTde0WNoSWaWr9wVcg@mail.gmail.com
    Backpatch-through: 18