Store interactive tool sessions in PostgreSQL database "gxitproxy" #1251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use PostgreSQL instead of SQLite to store interactive tool sessions. Requires galaxyproject/galaxy#18481, galaxyproject/gx-it-proxy#21. Closes usegalaxy-eu/issues#422.
Before merging, pay attention to the following.
gie_proxy_git_version
has been set to a revision that includes Add support for PostgreSQL galaxyproject/gx-it-proxy#21 (it should bev0.1.0
).Migration procedure:
gxitproxy
and set thegalaxy
user as its owner. Create also the tablegxitproxy
on beforehand (gx-it-proxy
refuses to run without it). For greater details you may have a look at the updated GTN training.psql
will complain about rows that already exist in the target table, but despite the complaint it will copy the rows which still are not in the target table.interactivetool_entry_point.job_id=job.id
. Filter the result by state different than "running". Encode all ids for interactive tool entry points and delete them from the gxitproxy table.Migration script: