WIP: t.sentinel.mask: Add postgresql option #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds two options to
t.sentinel.maskandi.sentinel.mask.workerin order to set the vector database connection in the temporary mapsets to PostgreSQL. This may be preferred because it was observed that using t.sentinel.mask with the default SQlite database on an NFS filesystem leads to long calculation times ofv.select(a step fromi.sentinel.mask.worker).please note
that postgresql needs to be properly installed and configured, and the database needs to be initialized and started for this option to work. See also: https://luppeng.wordpress.com/2020/02/28/install-and-start-postgresql-on-alpine-linux/