From: | Olivier MATROT <olivier(dot)matrot(at)accelis-sir(dot)fr> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Serialization exception : Who else was involved? |
Date: | 2014-11-25 11:59:43 |
Message-ID: | B67C2F6B6C7C57468D1BA9F176237121057478C3@pluton.Vepro.intra |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm using PostgreSQL 9.2.8 on Windows x64.
When a transaction as SERIALIZABLE isolation level is failing, is there
a way to know which connection(s), thus transaction(s), were involved in
the overall process ?
I'm working on an accounting database. I know that we should retry the
transaction, this is what we do. I've encountered an issue where a
transaction has to be run 10 times to succeed on a busy system.
There should be a serious problem here. I'm wondering if there is a
configuration parameter that would allow the system to tell in the
exception detail the other connections involved in the failure.
The Postgresql wiki on SSI has no such information.
Thanks is advance.
Olivier.
From | Date | Subject | |
---|---|---|---|
Next Message | Maila Fatticcioni | 2014-11-25 15:43:49 | Best filesystem for a high load db |
Previous Message | Deepti Sharma S | 2014-11-25 08:39:47 | FW: Latest Postgresql DB version |