Re: dispchar for oauth_client_secret

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: dispchar for oauth_client_secret
Date: 2025-04-15 22:25:43
Message-ID: CAGECzQQsJKwS2-PMSBaZ=tiZb6wtKMrvyYreYqWHeDBmq0AO-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 15 Apr 2025 at 22:48, Noah Misch <noah(at)leadboat(dot)com> wrote:
> yet be a
> postgres_fdw server option, postgres_fdw code can make it so. postgres_fdw
> already has explicit code to reclassify the "user" option.

I don't understand why it should be a server option instead of a user
mapping option. Having it be a server option means that *any* Postgres
user can read its contents. My knowledge on the purpose is pretty
limited, but having that be the case for something with "secret" in
the name seems very unintuitive.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Samokhvalov 2025-04-15 22:27:56 Re: Built-in Raft replication
Previous Message Ilia Evdokimov 2025-04-15 22:09:20 Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment