More PG Log - Mailing list pgsql-general

From Arvind Singh
Subject More PG Log
Date
Msg-id BLU164-W40331BC316934B419284F3CA480@phx.gbl
Whole thread Raw
In response to Re: PG Log  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: More PG Log
List pgsql-general
Oh, thankx for the answer on PG Log.
 
our postgres is on windows , it is version 9.0.5. There are a variety of applications, like CRM , Stockrelated
and now there is a online game based on it.
 
We are providing application development, statistics, datametrics support . For simple application and user settings
we use SqlLite and main application is on Postgres
 
PG Log is our only window to all the activies on DB Server and therefore it becomes very important especially to track
abnormal query or activities that are causing frequent errors. at any time we have aroung 10k entries waiting to be analyzed
for which we are building a customer application in c sharp, that matches our keywords.
 
For which,
 
Query 1
-----------
do we have a standard list of following Log Codes
- Command_tag ex. IDLE, SELECT ..
- error_severity , ex. FATAL, LOG .. 
- sql_state_code , ex. 00000, 08P01 ..
 
 
Query 2
----------

I have my CSV Log with lot of occurances of a certain Log select statement. 
-----------------------------------------------------------------------------------------------------
2012-03-28 19:25:48.015 IST,"postgres","stock_apals",2388,"localhost:1898",4f731863.954,7,"idle",2012-03-28 19:25:47 IST,2/98,0,LOG,00000,"statement: SELECT typname, oid FROM pg_type WHERE typname IN ('oidvector', '_oidvector', 'unknown', '_unknown', 'refcursor', '_refcursor', 'char', '_char', 'bpchar', '_bpchar', 'varchar', '_varchar', 'text', '_text', 'name', '_name', 'bytea', '_bytea', 'bit', '_bit', 'bool', '_bool', 'int2', '_int2', 'int4', '_int4', 'int8', '_int8', 'oid', '_oid', 'float4', '_float4', 'float8', '_float8', 'numeric', '_numeric', 'inet', '_inet', 'money', '_money', 'point', '_point', 'lseg', '_lseg', 'path', '_path', 'box', '_box', 'circle', '_circle', 'polygon', '_polygon', 'uuid', '_uuid', 'xml', '_xml', 'interval', '_interval', 'date', '_date', 'time', '_time', 'timetz', '_timetz', 'timestamp', '_timestamp', 'abstime', '_abstime', 'timestamptz', '_timestamptz')",,,,,,,,"exec_simple_query, .\src\backend\tcop\postgres.c:900",""
-----------------------------------------------------------------------------------------------------
 
Is is a performance concern. ?
is there anything that i can do to keep this statement from recurring.

 
 
Regards
arvind
 
 

 
> Subject: RE: [GENERAL] PG Log
> Date: Thu, 29 Mar 2012 10:49:20 +0200
> From: laurenz.albe@wien.gv.at
> To: arvindps@hotmail.com; pgsql-general@postgresql.org
>
> Arvind Singh wrote:
> > I have queries regarding columns in Postgres CSV Log.
> >
> > Following is a sample Logline
> >
> ------------------------------------------------------------------------
> > 2012-03-28 19:25:47.968
> IST,"postgres","stock_apals",2388,"localhost:1898",4f731863.954,6,"SET",
> 2012-
> > 03-28 19:25:47 IST,2/0,0,LOG,00000,"QUERY STATISTICS","! system usage
> stats:
> > ! 0.047000 elapsed 0.000000 user 0.000000 system sec
> > ! [0.078125 user 0.031250 sys total]",,,,,"Select * from stock_apals"
> > ,,"ShowUsage, .\src\backend\tcop\postgres.c:4305",""
> >
> ------------------------------------------------------------------------
> >
> > I am aware of all the data segments except the following
> >
> ------------------------------------------------------------------------
> > "! system usage stats:
> > ! 0.047000 elapsed 0.000000 user 0.000000 system sec
> > ! [0.078125 user 0.031250 sys total]",
> >
> ------------------------------------------------------------------------
> >
> > What do the number mean, it seems to appear only with a Logline for
> SQL statements
>
> These lines are emitted if you set log_statement_stats to "on".
>
> They contain execution statistics for the query. The "user" and "sys"
> times are acquired by the getrusage(2) or times(2) system call,
> depending
> on your operating system (on Windows, GetProcessTimes is used).
> You can look at the man page for your system for details.
>
> The values you see are:
> wall time, CPU user time and kernel CPU time it took to execute the
> query.
> The values in brackets are the values accumulated for this database
> session.
>
> Yours,
> Laurenz Albe

pgsql-general by date:

Previous
From: Vick Khera
Date:
Subject: Re: could not read block... how could I identify/fix
Next
From: Vick Khera
Date:
Subject: Re: could not read block... how could I identify/fix