Re: [rt-users] RT 4.4.1 and transaction isolation level on Postgres

2017-01-04 Thread Václav Ovsík
On Wed, Jan 04, 2017 at 04:50:11AM -0800, Alex Vandiver wrote: >... > MySQL suffers from the exact same problem -- but, as it happens, > both more silently and more catastrophically. See > https://github.com/bestpractical/rt/commit/e36364c5 Eh. I'm glad I did transition from Mysql to Postgres

Re: [rt-users] RT 4.4.1 and transaction isolation level on Postgres

2017-01-04 Thread Alex Vandiver
On Tue, 3 Jan 2017 17:06:47 +0100 Václav Ovsík wrote: > How about the Mysql don't have this problem - is this caused by > the different default transaction isolation level or not? MySQL suffers from the exact same problem -- but, as it happens, both more silently and more

Re: [rt-users] RT 4.4.1 and transaction isolation level on Postgres

2017-01-03 Thread Václav Ovsík
On Mon, Jan 02, 2017 at 08:10:15PM -0800, Alex Vandiver wrote: > On Mon, 2 Jan 2017 17:12:29 +0100 > Václav Ovsík wrote: > > Can anybody confirm on different system? > > Thanks for the detailed replication instructions. I can replicate, and > have tracked down a minimal

Re: [rt-users] RT 4.4.1 and transaction isolation level on Postgres

2017-01-02 Thread Alex Vandiver
On Mon, 2 Jan 2017 17:12:29 +0100 Václav Ovsík wrote: > Can anybody confirm on different system? Thanks for the detailed replication instructions. I can replicate, and have tracked down a minimal replication case. I'll drop my findings and suggestion on your ticket. The

[rt-users] RT 4.4.1 and transaction isolation level on Postgres

2017-01-02 Thread Václav Ovsík
Hi, to reproduce the deadlock problem with RT 4.4.1 on Postgres I tried to install RT 4.4.1 as clean new instalation: 1. On Debian 8.6 stable + Postgres 9.4 2. On Debian sid (unstable) + Postgres 9.6 (there was a need to change one sql command, option NOCREATEUSER -> NOCREATEROLE)