From: | Andrey Lizenko <lizenko79(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | rolled back transactions logging |
Date: | 2015-04-23 22:49:37 |
Message-ID: | CADKuZZBZRoPL0EP6dhKLme128i7Lp7hS2QVW=MR5qA2VhUj+Mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I can see that value pg_stat_database.xact_rollback for my db is instantly
growing, but I can not find a way to log these rolled back transactions
(or, may be, last statement within).
Even with
log_min_duration_statement = 0
log_statement = 'all'
there is no error messages in log.
I mean that I was expecting something like this (for example)
ERROR: value too long for type character varying(4096)
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
or to see ROLLBACK statement directly.
Can VACUUM be a reason of xact_rollback increasing?
Server version is 9.2.4
P.S,
Root problem is the number of wal files, it raised up significantly (more
than 4 times) with the same workload and I do not know why.
--
Regards, Andrey Lizenko
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-04-24 03:04:59 | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |
Previous Message | Tomas Vondra | 2015-04-23 21:12:16 | Re: BDR Across Distributed Nodes |