[Firebird-devel] CORE-5877 Garbage in the compound index after several updates

2018-07-20 Thread liviuslivius
Hi,   i ask here to not spam into the tracker. I know that indexes in Firebird are not transactional objects.   My understanding was that when we update record then old record vesion go to new place and new record version replace place where old record version was. This prevent for updating index

Re: [Firebird-devel] CORE-5877 Garbage in the compound index after several updates

2018-07-20 Thread Vlad Khorsun
20.07.2018 14:45, liviuslivius wrote: Hi, i ask here to not spam into the tracker. I know that indexes in Firebird are not transactional objects. My understanding was that when we update record then old record vesion go to new place and new record version replace place where old record version w

Re: [Firebird-devel] CORE-5877 Garbage in the compound index after several updates

2018-07-20 Thread livius
Not exactly so. When index key is not changed by UPDATE statement, engine doesn't add it into the index. Ok, so it has not changed. tx1: insert record (r1) with index key (k1) >> table contains one record version: r1-tx1 >> index contains one entry: (k2, r1) tx1: commit tx2: up

Re: [Firebird-devel] QA Tests

2018-07-20 Thread Adriano dos Santos Fernandes
On 20/07/2018 01:30, Dmitry Yemanov wrote: > 20.07.2018 04:59, Adriano dos Santos Fernandes wrote: >> >> When I run the QA tests, some tests results in FAIL and others result in >> ERROR. >> >> What is the differences between these results? > > FAIL means the test executed OK, but its output doesn