From: | "Aaron J(dot) Seigo" <aaron(at)gtv(dot)ca> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tim Holloway <mtsinc(at)southeast(dot)net> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] RFC: Industrial-strength logging |
Date: | 1999-10-25 21:50:59 |
Message-ID: | 99102515535807.00882@stilborne |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Byron Nikolaidis | 1999-10-25 23:36:52 | Re: [HACKERS] Re: [PATCHES] COMMENT ON patch |
Previous Message | Mike Mascari | 1999-10-25 19:30:56 | Re: [HACKERS] Re: [PATCHES] COMMENT ON patch |