Re: Postgres 9.3 beta log

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Arvind Singh <arvindps(at)hotmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres 9.3 beta log
Date: 2013-08-10 21:04:42
Message-ID: 20130810210442.GH30558@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Sat, Aug 10, 2013 at 09:52:48PM +0200, Stefan Kaltenbrunner wrote:
> On 08/10/2013 04:21 PM, Bruce Momjian wrote:
> > On Sat, Aug 10, 2013 at 06:38:57AM +0000, Arvind Singh wrote:
> >> as you can see it is for a single record "login88193" it places
> >>
> >> PARSER STATISTICS
> >> PARSE ANALYSIS STATISTICS
> >> REWRITER STATISTICS
> >>
> >> I know it appers because i have enabled log_parser_* options in log
> >>
> >> But what i request to know is the meaning of these statistics and how usefull
> >> is can be for a server load evaluation
> >
> > You should look get the getrusage manual pages for the meaning of the
> > values, and perhaps this for the meaning of these stages of a query:
> >
> > http://www.postgresql.org/developer/backend/
>
> true - but it seems a bit dubious that all of them show basically zero
> (or a constant time)

Yes, in an ideal world, the majority of time should be spent in the
executor. Those earlier stages are designed to set thing up for the
executor.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Brent Wood 2013-08-10 22:03:54 Re: earthdistance
Previous Message ascot.moss@gmail.com 2013-08-10 20:51:08 Replication delay

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2013-08-11 02:10:17 Re: killing pg_dump leaves backend process
Previous Message ascot.moss@gmail.com 2013-08-10 20:51:08 Replication delay