Fix creation and collation of vts_verification_str #1629
Merged
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.
What:
When creating SQL functions, it is first checked if the tables "nvts" and
"nvt_preferences" exist before trying to create vts_verification_str.
The function now also uses the collation "ucs_basic", which should be
available by default.
Why:
This addresses #1608 and an issue with new installations reported at https://community.greenbone.net/t/postgresql-error-when-running-latest-version-update-of-gvm-21-04/9625
How did you test it:
Checklist: