Open ggreggory-hub opened 1 month ago
seems that this bug related only to plume - it must activate first PK/UNIQUE indices, then FK indices, and only then other indices.
Actual bug is that while plume tries to create indexes in the correct order, it does not control that when creating of the FK is started, the corresponding PK\UK has already been created.
I apologize for misleading you. Error "internal Firebird consistency check (partner index description not found (175), file: idx.cpp line: 189)" was given in another example. In this example, this error was not returned.
It is not clear - if current example produce error (which?) or you have another one ?
An example without plume.
run the following bat file on the database obtained in step 1-3 from the top example
Will look at it, thanks. What settings is changed in firebird.conf ?
Can't reproduce any error
WI-V5.0.1.1469 Firebird 5.0
the sequence of actions: 1) I am creating a database using the ddl.sql script 2) I save the database in fbk 3) I restore from fbk with the option "Deactivate indexes" 4) I start multithreaded activation of indexes using plume (https://github.com/neozx/plume ):
plume -u SYSDBA -p masterkey -t 8 -d localhost:c:\database.fdb
activation fails with an error, some indexes are not activated. once there was an error "internal Firebird consistency check (partner index description not found (175), file: idx.cpp line: 189)"
ddl.zip