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

pg_cron SQL activation instructions are incorrect #28261

Closed
vickkhera opened this issue Jul 29, 2024 · 1 comment · Fixed by #28288
Closed

pg_cron SQL activation instructions are incorrect #28261

vickkhera opened this issue Jul 29, 2024 · 1 comment · Fixed by #28288
Labels
documentation Improvements or additions to documentation external-issue pr-opened A PR has been opened to resolve the issue

Comments

@vickkhera
Copy link

Improve documentation

Link

https://supabase.com/docs/guides/database/extensions/pg_cron?queryGroups=database-method&database-method=sql

Add a link to the page which needs improvement (if relevant)

Describe the problem

Is the documentation missing? Or is it confusing? Why is it confusing?

When following the SQL instructions on local development with the CLI, the first step specifies an incorrect schema:

postgres=> create extension pg_cron with schema extensions;
ERROR:  extension "pg_cron" must be installed in schema "pg_catalog"

That's on a freshly supabase db reset database with CLI version 1.187.8. When I try to activate it via the UI, it says it must be installed in the pg_catalog schema as well, so I did that in the CLI:

postgres=> create extension pg_cron with schema pg_catalog;
CREATE EXTENSION

which seems to work just fine.

Describe the improvement

A clear and concise description of the improvement.

Change the initial install step to use the correct schema, pg_catalog.

Additional context

Add any other context or screenshots that help clarify your question.

@vickkhera vickkhera added the documentation Improvements or additions to documentation label Jul 29, 2024
@encima
Copy link
Member

encima commented Jul 31, 2024

Thanks @vickkhera!

Good catch and opened a PR to address this

@encima encima added pr-opened A PR has been opened to resolve the issue and removed to-triage labels Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation external-issue pr-opened A PR has been opened to resolve the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants