| From: | Sean Chittenden <sean(at)chittenden(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PGBugs List <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: ALTER USER SET log_* not allowed... |
| Date: | 2004-11-09 19:05:48 |
| Message-ID: | 5DCB4FF0-3282-11D9-AF83-000A95C705DC@chittenden.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> Without USERLIMIT, we could easily change the rules to make ALTER USER
> work the way you want: we'd say you have to be superuser to issue ALTER
> USER or ALTER DATABASE with a SUSET variable (already true), and then
> the value can be adopted at session start in all cases since we can
> then
> treat pg_shadow and pg_database as secure sources.
Nevermind, you win. That's far more elegant/easier... is 8.0 looking
like a good time to make this break from tradition? -sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL Bugs List | 2004-11-09 21:01:41 | BUG #1308: Bug with JDBC driver on duplicate |
| Previous Message | Tom Lane | 2004-11-09 18:58:07 | Re: ALTER USER SET log_* not allowed... |