From: Tom Lane <tgl@sss.pgh.pa.us>
To: Uwe Bartels <uwe.bartels@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: docs log_executor_stats
Date: Mon, 22 Nov 2010 12:00:08 -0500
Message-ID: <28722.1290445208@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTi=kf4AeU-9g6NVdocPDxXZs3T9_cn7ULHYWy4vC@mail.gmail.com>
References: <AANLkTi=kf4AeU-9g6NVdocPDxXZs3T9_cn7ULHYWy4vC@mail.gmail.com>
Uwe Bartels <uwe.bartels@gmail.com> writes:
> i know what a context switch is or a page fault/reclaim, etc.
> what i need to know is the context of the numbers:
> - numbers without brackets
> - number with brackets
It looks like the numbers in brackets are the latest raw numbers from
getrusage(), whereas the numbers before the brackets are the delta
from a getrusage() call made at the start of execution.
> - context for those numbers: are all of these numbers one-to-one related to
> my function call? Or did those numbers (signals/page reclaims) come up
> during the time of execution of that function?
It's just the overall getrusage result for the backend process.
> what I don't know and never found so far is "Local blocks" and "Direct
> blocks". So I'd be interested to know what's this, jst for completeness.
Local blocks are (or were ... that code is gone as of 9.0) I/O for
temporary tables of the current backend. I think direct blocks was a
count of I/Os on temp files (sort data and so on).
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, uwe.bartels@gmail.com
Subject: Re: docs log_executor_stats
In-Reply-To: <28722.1290445208@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox