From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tim Holloway <mtsinc(at)southeast(dot)net> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, "Aaron J(dot) Seigo" <aaron(at)gtv(dot)ca>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tim Holloway <mtsinc(at)leading(dot)net>, pgsql-admin(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [ADMIN] Re: [HACKERS] RFC: Industrial-strength logging (longmessage) |
Date: | 1999-10-26 05:27:54 |
Message-ID: | 199910260527.BAA21909@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I think we have a consensus. Destroy and recreate logging
> data structures/tasks on receipt of
> suitable event.
>
> For simple things like log levels, though, I'd still like
> feedback on
> desirablility and feasibility of altering basic logging
> options though
> (authorized!) frontends. As a user, I get nervous when I
> have to thread
> my way past possibly-fragile unrelated items in a config
> file when I'm trying
> to do a panic diagnosis. As an administrator, I get even
> MORE nervous if one
> of the less careful people I know were to be entrusted with
> that task.
One more item I have not heard is that you can create virtual table that
look like tables but return data about users, queries on SELECT.
Informix does this. Allows you to get info, without the need for
storage. Not good for every case, but an interesting idea sometimes.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-10-26 06:16:12 | Re: [HACKERS] Logging - pg_options format change? |
Previous Message | Bruce Momjian | 1999-10-26 05:25:43 | Re: [HACKERS] Function-manager redesign: second draft (long) |