>
> > 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...
A most meritorious suggestion! Also one that I can implement
fairly easily, I think.
>
> of course, once we have the logs, the next step would be to write a script
> that imports them into a pgsql database @;-)
I'll even go you one better and make it so the data is in
directly importable format. That way
you can set up a log database and each file becomes a table,
with appropriate linkages. All this without
sacrificing the ability to do a consolidated log as well (I
/said/ I had a powerful framework!).
Of course, you realize that the act of importing the
logfiles into PostgreSQL is ITSELF
a loggable event!
>
> - --
> Aaron J. Seigo
> Sys Admin
>
> ------------------------------
>
************