Re: [Gnumed-bugs] <bug>: popped up

[Karsten Hilbert]

Hi Marc,

thanks for reporting this problem.

> user comment  : popped up
> 
> client version: 1.6.7

What you see:

> 2016-07-19 13:37:21  ERROR     gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::run_rw_queries() #1688): RW 
> query failed: [
>                       SELECT * FROM clin.v_narrative
>                       WHERE
>                               pk_narrative = 
> currval(pg_get_serial_sequence('clin.clin_narrative', 'pk'))]
> 2016-07-19 13:37:21  ERROR     gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::run_rw_queries() #1692): PG 
> error code: 40001
> 2016-07-19 13:37:21  ERROR     gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::run_rw_queries() #1694): PG 
> error message: ERROR:  could not serialize access due to read/write 
> dependencies among transactions
> DETAIL:  Reason code: Canceled on identification as a pivot, during conflict 
> out checking.

is PostgreSQL preventing us from clobbering data in the
database. It seems like a transient error which can occur
when, say, two clients happen to do about the same thing to a
patient.

Can you reproduce this issue or remember more precisely the
exact circumstances under which it happened ?

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346