Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

On Thu, Apr 28, 2016 at 11:39 AM, Ann Harrison wrote: A lot of stuff including: > In ancient history, even in read-committed mode, Firebird blocked > transactions from updating records if the most recent version was created > by a concurrent transaction. At the time,

RE: [firebird-support] Re: SELECT WITH LOCK, WAIT transaction, deadlock

Dmitry, > 28.04.2016 16:19, Gabor Boros wrote: > > > In the language reference for "isc_tpb_read_committed + isc_tpb_wait" > > I see this: "Update conflict exceptions can never be raised by an > > explicit lock statement in this TPB mode." > > This is true for two concurrent transactions but

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

On Thu, Apr 28, 2016 at 2:16 PM, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: > ... > > Try to utilize WITH LOCK because I need many unique number generators in > a table field. Like a generator/sequence but under transaction control. > Okay...

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

2016. 04. 28. 17:46 keltezéssel, Thomas Steinmaurer t...@iblogmanager.com [firebird-support] írta: > What happens if you are running Read Committed WITH record version? No error with 10 concurrently instances of the test app (2 SQL lines (SELECT ... WITH LOCK and UPDATE ...)). But failing with

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

> 2016. 04. 28. 14:55 keltezéssel, Dimitry Sibiryakov s...@ibphoenix.com > [firebird-support] írta: >> 28.04.2016 13:41, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: >>> The message is: >>> deadlock >>> update conflicts with concurrent update >>> concurrent transaction number is ...

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

On Thu, Apr 28, 2016 at 9:19 AM, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: > 2016. 04. 28. 14:55 keltezéssel, Dimitry Sibiryakov s...@ibphoenix.com > [firebird-support] írta: > > 28.04.2016 13:41, Gabor Boros gaborbo...@yahoo.com

[firebird-support] Re: SELECT WITH LOCK, WAIT transaction, deadlock

28.04.2016 16:19, Gabor Boros wrote: > In the language reference for "isc_tpb_read_committed + isc_tpb_wait" I > see this: "Update conflict exceptions can never be raised by an explicit > lock statement in this TPB mode." This is true for two concurrent transactions but may fail for three or

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

2016. 04. 28. 13:36 keltezéssel, Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] írta: > 28.04.2016 13:30, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: >> Now 3 instances enough to got deadlock after some time. > >Are you sure that error you got is "deadlock" and not

[firebird-support] Re: Installing Firebird 3.0 alongside Firebird 2.5 and 2.1

Thanks Thomas. I have used some of this as well :)

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

2016. 04. 28. 14:55 keltezéssel, Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] írta: > 28.04.2016 13:41, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: >> The message is: >> deadlock >> update conflicts with concurrent update >> concurrent transaction number is ... > >

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

28.04.2016 13:41, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: > The message is: > deadlock > update conflicts with concurrent update > concurrent transaction number is ... That's an expected behavior. -- WBR, SD.

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

2016. 04. 28. 13:36 keltezéssel, Dimitry Sibiryakov s...@ibphoenix.com [firebird-support] írta: > 28.04.2016 13:30, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: >> Now 3 instances enough to got deadlock after some time. > >Are you sure that error you got is "deadlock" and not

[firebird-support] Re: Installing Firebird 3.0 alongside Firebird 2.5 and 2.1

Thanks Mark (and all others). I think I have succesfully installed FB 3.0 alongside the other. In legacy mode. This is perfect for testing. Now I'm strucling with GDS32.DLL. We still have programs, which uses these connections. According to:

Re: [firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

28.04.2016 13:30, Gabor Boros gaborbo...@yahoo.com [firebird-support] wrote: > Now 3 instances enough to got deadlock after some time. Are you sure that error you got is "deadlock" and not "update conflict"? -- WBR, SD.

[firebird-support] SELECT WITH LOCK, WAIT transaction, deadlock

Hi All, I tested the WITH LOCK feature in July of 2014 with 3.0 and a simple application and works like a charm. Now I want to use it in production but the same test app give deadlocks. The database contains one table with one row and a BIGINT field increased by 1 500 times by the test app.