-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not use postgres extensions dblink and pgcrypto #9367
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just small nitpick. But I wonder how to approach this. Do we just merge this into uyuni and see what happens, or should we have separate branch for this.
Apparently dblink was used as a simulation of autonomous transaction, whatever it means.
if [[ "$s" == *oracle ]]; then | ||
db="oracle" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we kick those 2 lines out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whole schema/sm-specific-schema-patches
seems to be obsolete and can be dropped, IMHO. It has not been touched since 2018. But that is for another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this was needed when spacewalk had incompatible changes compared to SUMA and we had to copy them again and again over. We can remove this
I saw no upgrade script... is that intended? How would that fly with upgrades? |
648a7cf
15efb4a
to
648a7cf
Compare
Fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question, other then that all looks good to me
-- granted to use or replicate Red Hat trademarks that are incorporated | ||
-- in this software or its documentation. | ||
|
||
create or replace function pg_dblink_exec(in_sql in varchar) returns void as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also remove this function from the upgrade script?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing a function removal in the update script. The rest LGTM
-- granted to use or replicate Red Hat trademarks that are incorporated | ||
-- in this software or its documentation. | ||
|
||
create or replace function pg_dblink_exec(in_sql in varchar) returns void as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is needed.
What does this PR change?
This PR drops postgres extensions dblink and pgcrypto. This makes use of external database easier.
The extensions seem to be no longer used.
pgcrypto is not used since #8045
dblink is used in function pg_dblink_exec. This function is never called.
GUI diff
No difference.
Documentation
Test coverage
No tests: already covered
DONE
Links
Issue(s): https://github.com/SUSE/spacewalk/issues/25363
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:
Before you merge
Check How to branch and merge properly!