From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Cc: PostgreSQL-documentation <docs@postgreSQL.org>
Subject: Re: [HACKERS] SESSION_USER
Date: Fri, 14 Apr 2000 17:30:14 -0400
Message-ID: <4562.955747814@sss.pgh.pa.us> (raw)
In-Reply-To: <200004142035.QAA04417@candle.pha.pa.us>
References: <200004142035.QAA04417@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> create_table.sgml mentions SESSION_USER is not supported. I don't think
> that is true anymore, is it?
regression=# select session_user;
getpgusername
---------------
postgres
(1 row)
Looking at the spec, we do seem to be missing SYSTEM_USER out of the
four variants the spec mentions. However, considering that we map
them all to the same thing anyway, I can't get too excited about it.
If something is done about making functions have setuid-like behavior,
we'd want to make sure that the appropriate ones of these functions
change value inside a function.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, pgsql-hackers@postgreSQL.org, docs@postgreSQL.org
Subject: Re: [HACKERS] SESSION_USER
In-Reply-To: <4562.955747814@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox