Re: [HACKERS] RFC: Industrial-strength logging - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] RFC: Industrial-strength logging
Date
Msg-id Pine.BSF.4.10.9910252159380.404-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] RFC: Industrial-strength logging  ("Aaron J. Seigo" <aaron@gtv.ca>)
List pgsql-hackers
On Mon, 25 Oct 1999, Aaron J. Seigo wrote:

> hi...
> 
> > What about
> > SET LOGLEVEL TO <something>;
> > SET LOGDETAIL TO <something>;
> > or the like. You could use pg_shadow.usesuper as a security stipulation.
> > Using something like a signal to do this is probably overkill, especially
> > since there are hardly any left, and it's also infinitely less intuitive
> > and flexible.
> 
> this would be done from psql? if so, here's a query i have: are there any plans
> to seperate the admin functions out of psql and into another seperate tool? 
> 
> i have a queasyness with general users having access to a tool that can
> do admin takss (even if they supposedly don't have a superuser account).

There is no such thing, actually...all "admin commands" are seperate SQL
queries...psql is merely one of many interfaces that allows one to talk to
and send queries to the backend...what the backend then does with the
query is where the security lies...

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



pgsql-hackers by date:

Previous
From: Tim Holloway
Date:
Subject: Logging - pg_options format change?
Next
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Re: [GENERAL] Postgres INSERTs much slower than MySQL?