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

From Aaron J. Seigo
Subject Re: [HACKERS] RFC: Industrial-strength logging
Date
Msg-id 99102515535807.00882@stilborne
Whole thread Raw
In response to Re: [HACKERS] RFC: Industrial-strength logging  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [HACKERS] RFC: Industrial-strength logging  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
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).

it also seems much cleaner to have admin in one tool and data interaction in
another.

am i off track here?

-- 
Aaron J. Seigo
Sys Admin


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] RFC: Industrial-strength logging
Next
From: Byron Nikolaidis
Date:
Subject: Re: [HACKERS] Re: [PATCHES] COMMENT ON patch