Re: SYSTEM_USER reserved word implementation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joe Conway <mail@joeconway.com>
Cc: Jacob Champion <jchampion@timescale.com>,
"Drouvot,
Bertrand" <bdrouvot@amazon.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-06-22T16:28:43Z
Lists: pgsql-hackers
Joe Conway <mail@joeconway.com> writes: > On 6/22/22 11:52, Tom Lane wrote: >> I think a case could be made for ONLY returning non-null when authn_id >> represents some externally-verified identifier (OS user ID gotten via >> peer identification, Kerberos principal, etc). > But -1 on that. > I think any time we have a non-null authn_id we should expose it. Are > there examples of cases when we have authn_id but for some reason don't > trust the value of it? I'm more concerned about whether we have a consistent story about what SYSTEM_USER means (another way of saying "what type is it"). If it's just the same as SESSION_USER it doesn't seem like we've added much. Maybe, instead of just being the raw user identifier, it should be something like "auth_method:user_identifier" so that one can tell what the identifier actually is and how it was verified. regards, tom lane
Commits
-
Introduce SYSTEM_USER
- 0823d061b0b7 16.0 landed
-
Add some information about authenticated identity via log_connections
- 9afffcb833d3 14.0 cited