Re: ALTER USER SET log_* not allowed...

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: Andrew McMillan <andrew(at)catalyst(dot)net(dot)nz>, Sean Chittenden <sean(at)chittenden(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PGBugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: ALTER USER SET log_* not allowed...
Date: 2004-11-10 18:19:38
Message-ID: 14379.1100110778@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Why not? You can put whatever restrictions you like in such a function.

> I assume to do this in a function you would have to create a temp table
> to store the original setting?

Not at all. You could use "RESET foo" to see what the "original" value
of foo was.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2004-11-10 21:34:17 Missing Tablespace link error message misleading
Previous Message Bruce Momjian 2004-11-10 18:17:16 Re: ALTER USER SET log_* not allowed...