Thanks again,
I have come across a very peculiar situation.
We have a postgres installation 9.0. It was installed last year.
But we started implementation on it, just recently.
And therefore the need to develop a Logparser application.
During our preliminary parsing , What we discovered is just beyond the grasp of my knowledge.
It seems that during a certain period lastyear in November, it created a Session entry that holds more than
Fifty thousand records for a SINGLE SESSION (4ebccaa2.20c) . Yes that is 5 with five zeros
One does look at wonder of the Dawn of November when such occurance holds place.
Is it divine intervention, because we never parsed the log in those days and therefore cannot ascertain the reasons for such verbosity.
Although it never reoccurs and luckily we had csv option on during that period.
Where should i report such findings
I have uploaded that Part of Log at
http://dl.dropbox.com/u/71964910/pg_log_with_lot_of_session.zip arvind
- ------------------------------------------------------
- The woods are lovely, dark, and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep. - (Robert Frost, Stopping by Woods on a Snowy Evening)
> Subject: RE: [GENERAL] application for postgres Log
> Date: Fri, 14 Sep 2012 13:16:33 +0200
> From: laurenz.albe@wien.gv.at
> To: arvindps@hotmail.com; pgsql-general@postgresql.org
>
> Arvind Singh wrote:
> > I have enabled the csvlog option.
> >
> > There seem to be 24 columns in the Log. I have difficulty in
> understanding the following columns
> >
> > - virtual_transaction_id
>
> Such a transaction ID is given to every transaction.
> Can be used to track transactions in the log.
>
> > - transaction_id
>
> Such a transaction ID is given to a transaction
> that modifies the database.
>
> > - hint
>
> Part of the error message (like "detail" and "context").
>
> > - internal_query
> > - internal_query_pos
>
> These are used a handful of times in the code, I'm not
> 100% sure what for.
> You may never encouter one of those.
>
> > - context
>
> Describes where the error ocurred.
>
> Yours,
> Laurenz Albe
