Opened 10 years ago
Closed 10 years ago
#622 closed defect (wontfix)
rasdaman 9.0 fails when the database is not update
| Reported by: | Dimitar Misev | Owned by: | Kinga Lipskoch |
|---|---|---|---|
| Priority: | major | Milestone: | 9.0.x |
| Component: | lockmgr | Version: | development |
| Keywords: | Cc: | Peter Baumann | |
| Complexity: | Medium |
Description (last modified by )
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 by , 10 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
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:5 by , 10 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
As short term solution, please first run 'update_sh'.