On Tue, Jul 10, 2018 at 11:38 AM, Justin Pryzby
wrote:
>
> > 2. Make stats available in `pg_stat_statements` (or alternate view that
> > could be joined on). The block stats are already available here, but
> > others like CPU usage, page faults, and context switches are not.
>
> pg_stat_statements
In this case this happens because the update modifies several rows and
different transactions may try to modify those rows (and obtain locks for them)
in different order.
E.g. one transaction first gets row 1 and then row 2, and the second
transaction first updates row 2 and then row 1.
The onl
Hi,
All.
Can anyone give me a hand?
I meet a problem:High concurrency but simple updating causes deadlock
1.System info
Linux version 4.8.0
Ubuntu 5.4.0-6ubuntu1~16.04.4
2.Pg info
PostgreSQL 9.5.12 on i686-pc-linux-gnu, compiled by gcc (Ubuntu
5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609, 32-bit