From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Missing variable "role" in "pg_settings"? |
Date: | 2005-11-05 19:08:49 |
Message-ID: | 17919.1131217729@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-general |
"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> The per-session variable "role" is not shown when
> doing "select pg_settings". It is, however, possible
> to set it using "set role ...", and to query it using
> "show role". Is this per design, or is this a bug.
It's marked NO_SHOW_ALL in guc.c. I'm not sure about the reasoning
for this --- session_authorization is the same way, and we probably
just copied that when we made the role variable; but I've forgotten
what the rationale for marking session_authorization as NO_SHOW_ALL
was.
> In case omiting role from pg_settings is per design,
> how could pgadmin find _all_ variables that can be set per user?
If this is an argument for not having *any* NO_SHOW_ALL variables,
I think the answer will be "no".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Berend Tober | 2005-11-05 19:09:40 | Re: Duplicate Row Removal |
Previous Message | Florian G. Pflug | 2005-11-05 17:49:38 | Re: Missing per-user variable? |
From | Date | Subject | |
---|---|---|---|
Next Message | Berend Tober | 2005-11-05 19:09:40 | Re: Duplicate Row Removal |
Previous Message | Martijn van Oosterhout | 2005-11-05 18:47:31 | Re: joining a query with a select count(*) |