Issue Details (XML | Word | Printable)

Key: CORE-1725
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Dmitry Yemanov
Votes: 2
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Unable to restore a database with inactive indices if any SP/trigger contains an explicit plan

Created: 04/Feb/08 06:00 AM   Updated: 06/Jul/20 05:12 AM
Component/s: Engine
Affects Version/s: 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.1 RC1
Fix Version/s: None

Issue Links:
Duplicate
 

QA Status: Done successfully
Test Details:
::: NB ::: This bug was fixed between 17-dec-2018 and 23-jan-2019.
Builds 4.0.0.1346 and 3.0.5.33084 (both of 17.12.2018) still have bug: no program units will be in restored DB.
Builds 4.0.0.1391 (23.01.2019) and 3.0.5.33097 (01.02.2019) work fine.

Ticket state can be changed to resolved / fixed.


 Description  « Hide
gbak -r -i <backup path> <database path>. Note the -i switch which is expected to deactivate the indices (e.g. backup contains duplicates in PK). Now, if any PSQL code contains an explicit plan referencing any indices, then the restore fails:

gbak:creating indexes
gbak: committing metadata
gbak: ERROR:<index name> cannot be used in the specified plan
gbak:Exiting before completion due to errors

At this point, tables with data are restored fine but all the PSQL objects are lost.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.