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

Allow non-public Postgres schema #1196

Closed
zhukau opened this issue May 9, 2016 · 0 comments
Closed

Allow non-public Postgres schema #1196

zhukau opened this issue May 9, 2016 · 0 comments

Comments

@zhukau
Copy link
Contributor

zhukau commented May 9, 2016

If using custom schema in Postgres, i.e. - kong, instead of public Kong works until first restart/reload.
Then it fails with error message Error during migration 2015-01-12-175310_init_schema: ERROR: relation "custom_id_idx" already exists caused by hardcoded public schema name in database objects existence checks.

While it is nice to have a configurable schema name as suggested in issue #1193, in reality we can rely on search_path configured on database level and its default value $user, public that covers 99% of use cases.

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

No branches or pull requests

3 participants