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: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "is_superuser" parameter creates inconsistencies
Date: 2003-08-31 23:10:18
Message-ID: 29512.1062371418@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Bruce Momjian writes:
>> Is this a TODO item or something we want to address for 7.4?

> I'd like to address it for 7.4, but it looks a bit more difficult than it
> seemed at first, because session_user isn't in GUC at all, so there is no
> infrastructure to pass it to the client.

We'd have to add it, presumably as a read-only variable. I didn't think
that was particularly difficult though ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-31 23:17:59 Re: massive quotes?
Previous Message Tom Lane 2003-08-31 23:06:38 Preliminary notes about hash index concurrency (long)