|
Date: 2006-02-24 01:45
Sender: seanleyne Logged In: YES user_id=71163 Vlad, Please clarify. Was this a real database corruption which GFIX was reporting or an anomoly due to some disk pages/structures not being created which GFIX was expecting to find? Date: 2006-02-23 13:26
Sender: hvlad Logged In: YES user_id=879552 Now 'create index' will request protected_read lock on relation. This means that if you have active transaction in which you perform insert\update\delete on relation 'create index' will wait (or no_wait - it depends on transaction parameters) until modifying transaction ends. And vice versa - you can read but not write relation until index build is finished Date: 2006-02-23 12:35
Sender: ceeam Logged In: YES user_id=1457907 Confirmed. ;) Tried build 12345 - now attempt to add/change index to table active in other transaction (and I think it goes for any other meta-changes) results in "object in use" error (with no_wait transaction of course). Well - it's better than corrupted DBs, I think. Thanks guys! Date: 2006-02-22 16:04
Sender: hvlad Logged In: YES user_id=879552 As i understand this bug is very old and must exists in all versions of FB Fixed in build 12333. Confirm please Date: 2006-02-21 19:40
Sender: ceeam Logged In: YES user_id=1457907 Firebird 2.0 (Beta 2, though I noticed it first during Alfa 1, yes, I did backup/restore during update). Superserver. WinXP SP2 (FAT32 partition if that matters). Date: 2006-02-21 19:35
Sender: seanleyne Logged In: YES user_id=71163 Please confirm the FB version you are running and the platform/OS. |
||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Major
Adding index during DB activity causes GFIX errors
Sender: hvlad
Logged In: YES
user_id=879552
As i understand some record versions created while index
build is not indexed. Error :
Index %d is corrupt (missing entries)
tell us exactly that. I'd say it is a real corruption
Fix prevents relation modifications until then while the index
will not be constructed completely. If somebody knows how
to construct a correct index and not forbid concurrent relation
modifications i am glad to learn it :)