Opened 3 years ago

Closed 3 years ago

#622 closed defect (wontfix)

rasdaman 9.0 fails when the database is not update

Reported by: dmisev Owned by: klipskoch
Priority: major Milestone: 9.0.x
Component: lockmgr Version: development
Keywords: Cc: pbaumann
Complexity: Medium

Description (last modified by dmisev)

The latest rasdaman 9.0 will fail to execute queries if the database has not yet been updated with update_db.sh, with the following error:

rasdaman error 4000: Error: One or more of the target tiles are locked by another transaction.

This should not happen, tile locking should be simply disabled when the locking table is not present in RASBASE. To reproduce:

psql -d RASBASE
drop table RAS_LOCKEDTILES;

and then run any rasql query.

After update_db.sh rasql executes queries fine, however directql (in source:applications/directql) still fails with the same error.

Change History (5)

comment:1 Changed 3 years ago by dmisev

  • Description modified (diff)

comment:2 Changed 3 years ago by klipskoch

As short term solution, please first run 'update_sh'.

comment:3 Changed 3 years ago by klipskoch

I just submitted the patch for the partial fix.
The database connection and disconnection for the lockmanager is included in directql.
Select is fixed.
I did not test other type of queries.

comment:4 Changed 3 years ago by dmisev

  • Priority changed from critical to major

Lockmgr is optional now, so lowering prio.

comment:5 Changed 3 years ago by dmisev

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.