| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, PostgreSQL-documentation <docs(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] SESSION_USER |
| Date: | 2000-04-14 21:30:14 |
| Message-ID: | 4562.955747814@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-04-14 22:07:56 | Doc TODO list is done |
| Previous Message | Bruce Momjian | 2000-04-14 20:35:28 | SESSION_USER |