Message-ID: <5113FF56.5020309@pinpointresearch.com>
Date: Thu, 07 Feb 2013 11:24:06 -0800
From: Steve Crawford <scrawford@pinpointresearch.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Milos Gajdos <gy2kre@centrum.cz>, pgsql-admin@postgresql.org
Subject: Re: Postgres 9.1 statistics in pg_stat_database
References: <20130207191641.149E5128@centrum.cz>
	<17450.1360263900@sss.pgh.pa.us>
In-Reply-To: <17450.1360263900@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 02/07/2013 11:05 AM, Tom Lane wrote:
> =?utf-8?q?Milos_Gajdos?= <gy2kre@centrum.cz> writes:
>> What this shows is that xact_commit increases by 3 after just one row insert. tup_inserted does seem to report correct value. After simple SELECT, xact_commit increases by 2 - kind of strange as SELECT shouldn't really be increasing xact_commit ?
> Yes, a SELECT does count as an xact_commit...
>
Additionally (correct me if I'm wrong, Tom), background activity like 
autovacuum will generate countable transactions. I can see transactions 
increment by a dozen or more on a completely "idle" database if I just 
wait a minute or two but the number of those transactions, while visible 
on an idle system, is lost in the noise on a busy database.

Other things that generate transactions include connecting to the 
database (one, it appears) but \d in psql appears to generate a minimum 
of four.

Cheers,
Steve


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin