From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: System username in pg_stat_activity |
Date: | 2024-01-10 13:27:50 |
Message-ID: | 874jflmi7d.fsf@wibble.ilmari.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Wed, Jan 10, 2024 at 1:44 PM Aleksander Alekseev
> <aleksander(at)timescale(dot)com> wrote:
>>
>> It hurts my sense of beauty that usename and authname are of different
>> types. But if I'm the only one, maybe we can close our eyes on this.
>> Also I suspect that placing usename and authname in a close proximity
>> can be somewhat confusing. Perhaps adding authname as the last column
>> of the view will solve both nitpicks?
>
> But it should probably actually be name, given that's the underlying
> datatype. I kept changing it around and ended up half way in
> between...
https://www.postgresql.org/docs/current/functions-info.html#FUNCTIONS-INFO-SESSION-TABLE
(and pg_typeof(system_user)) says it's text. Which makes sense, since
it can easily be longer than 63 bytes, e.g. in the case of a TLS client
certificate DN.
- ilmari
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2024-01-10 13:32:50 | Re: Custom explain options |
Previous Message | Konstantin Knizhnik | 2024-01-10 13:27:06 | Re: Custom explain options |