Skip site navigation (1) Skip section navigation (2)

Re: "is_superuser" parameter creates inconsistencies

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "is_superuser" parameter creates inconsistencies
Date: 2003-07-28 14:28:25
Message-ID: 9196.1059402505@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Presumably, the "is_superuser" parameter was intended to make the updating
> of psql's prompt more accurate when SET SESSION AUTHORIZATION is used.
> However, if the prompt is customized to include the user name (%n), then
> the prompt changes to reflect the real superuser status, but does not
> change the user name.  I guess we need to pass "session_user" as well.

Seems reasonable.  IIRC the only addition needed to the server code is
to set a flag in the variable's GUC entry.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Aizaz AhmedDate: 2003-07-28 14:41:29
Subject: Re: [HACKERS] allowed user/db variables
Previous:From: Tom LaneDate: 2003-07-28 14:26:52
Subject: Re: Passing server_encoding to the client is not future-proof

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group