Skip to content
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

Prefix pgcrypto hmac function with @extschema@ #10

Merged
merged 1 commit into from
Dec 23, 2018
Merged

Prefix pgcrypto hmac function with @extschema@ #10

merged 1 commit into from
Dec 23, 2018

Conversation

twopoint718
Copy link
Contributor

This PR resolves #6

It sounds like, quoting the Postgres docs:

https://www.postgresql.org/docs/10/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION

If any prerequisite extensions are listed in requires in the control file, their target schemas are appended to the initial setting of search_path. This allows their objects to be visible to the new extension's script file.

pgcrypto is listed in the control file so it should be available within this extension via @extschema@. And indeed, this fixes the issue for me.

Thanks!

@michelp michelp merged commit 3532a73 into michelp:master Dec 23, 2018
@michelp
Copy link
Owner

michelp commented Dec 23, 2018

Thanks @twopoint718 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failure when pgcrypto is loaded into a schema.
2 participants