Let me show you my statistics, that confuses me even in terms of this
discussion.
What am I doing.
1. Create a database *highload*.
2. Execute *select xact_commit from pg_stat_database where datname =
'highload'* from neighbouring database (so that xact_commit is counted to
that neighbour) and rec
Steve Crawford writes:
> Additionally (correct me if I'm wrong, Tom), background activity like
> autovacuum will generate countable transactions.
Yes, absolutely.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to yo
On 02/07/2013 11:05 AM, Tom Lane wrote:
=?utf-8?q?Milos_Gajdos?= 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 b
=?utf-8?q?Milos_Gajdos?= 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
I've been searching for some information about Postgres 9.1 stats which are
stored in pg_stat_database - on the web and on IRC. I found SOME information
for 9.2 but even that doesn't seem to be accurate. What I'm after is to get
proper transaction stats ie commits and rollbacks. Also I've no clu
