Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Remove GUC USERLIMIT variable category, making the affected

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Remove GUC USERLIMIT variable category, making the affected
Date: 2004-11-14 21:06:23
Message-ID: 26274.1100466383@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Sean Chittenden <sean(at)chittenden(dot)org> writes:
>> Also delay processing of options received in
>> client connection request until after we know if the user is a 
>> superuser,
>> so that SUSET values can be set that way by legitimate superusers.

> Does this mean that postgresql.conf:log_connection=off, ALTER USER usr 
> SET log_connection=on will only result in a log entry after we've 
> processed useconfig?

It won't result in a log entry at all, and never has, because
log_connection executes long before we look at the options.

			regards, tom lane

In response to

pgsql-committers by date

Next:From: Bruce MomjianDate: 2004-11-14 21:33:11
Subject: pgsql: Remove replicaiton FAQ item.
Previous:From: Sean ChittendenDate: 2004-11-14 20:54:23
Subject: Re: pgsql: Remove GUC USERLIMIT variable category, making the affected

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group