> hi..
>
> > that. Having made that constraint, I see 3 contexts:
> >
> > 1) Server events. E.g.:
> > 2) User sessions.
> > 3) Transactions.
> >
>
> how about 3 different logs? pg_server.log, pg_sessions.log, pg_trans.log or
> something along those lines.. that way you could parse each file as they would
> each have a consistent record format...
>
> of course, once we have the logs, the next step would be to write a script
> that imports them into a pgsql database @;-)
We definately need better logging, it is just that none of us have
gotten involved in it. We do have syslog capabilites, and several
logging levels. 7.0 has improved logging printing with -d output. I
found the 6.5.* tree had some bugs in that area, or maybe the bugs were
introduced after 6.5.*. Please check what we have, get consensus on
improvements, and submit a patch. We are ready to receive.
--
Bruce Momjian | http://www.op.net/~candle
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
************
