Re: 7.4 beta 1: SET log_statement=false

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bertrand Petit <pgsql-bugs(at)phoe(dot)frmug(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: 7.4 beta 1: SET log_statement=false
Date: 2003-08-13 19:27:30
Message-ID: 10373.1060802850@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers pgsql-patches

Bertrand Petit <pgsql-bugs(at)phoe(dot)frmug(dot)org> writes:
> Non superusers can set log_statement to true but can't set it
> back to false even if log_statement was false at the begining of a
> connection.

Yeah. I think that the restrictions for USERLIMIT variables ought to
compare against the reset_val, not the session_val.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2003-08-13 22:05:46 Re: [BUGS] 7.4 beta 1: SET log_statement=false
Previous Message Tom Lane 2003-08-13 14:15:30 Re: Partial Indexes condtions

Browse pgsql-hackers by date

  From Date Subject
Next Message Frank Wiles 2003-08-13 19:47:12 Re: Speeding up operations
Previous Message Andreas Pflug 2003-08-13 16:52:37 Re: reuse sysids security hole?

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2003-08-13 21:07:46 logging enhancements, minor code cleanup (retry)
Previous Message Bertrand Petit 2003-08-13 12:56:45 7.4 beta 1: SET log_statement=false