New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding index during DB activity causes GFIX errors [CORE75] #399
Comments
Commented by: Alice F. Bird (firebirds) Date: 2006-02-24 08:18 As i understand some record versions created while index 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 |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-24 01:45 Vlad, Please clarify. Was this a real database corruption which |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-23 13:26 Now 'create index' will request protected_read lock on |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-23 12:35 Confirmed. ;) |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-22 16:04 As i understand this bug is very old and must exists in all |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-21 19:40 Firebird 2.0 (Beta 2, though I noticed it first during Alfa |
Commented by: Alice F. Bird (firebirds) Date: 2006-02-21 19:35 Please confirm the FB version you are running and the |
Modified by: @pcisarWorkflow: jira [ 10099 ] => Firebird [ 14281 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: ceeam (ceeam)
SFID: 1436066#
Submitted By: ceeam
I have a local app using FB DB. When background
process is working (adding lots of records to ITEM
table and related tables) and I add an index to ITEM
(by primary key field, descending, using IBExpert)
this causes later "index page error(s)" from "gfix -v -
full" ("gfix -v" does not complain). Here's firebird.
log line:
Index 3 is corrupt (missing entries) in table ITEM (
131)
It is pretty well reproduceable. Droping this index
and later re-creating it (during idle time) "fixes"
the DB. If you need further details please contact me:
mailto:cyrixm@gmail.com.
The text was updated successfully, but these errors were encountered: