You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
====== 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.
The text was updated successfully, but these errors were encountered:
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.
Submitted by: @dyemanov
Is duplicated by CORE6350
Votes: 2
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.
====== 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.
The text was updated successfully, but these errors were encountered: