DigitalOcean support pg_cron
extension for managed Postgres database service,
but we cannot use it since we cannot change the extension’s database since we cannot change the postgresql.conf
, so extension can only be used with defaultdb
. Typically using defaultdb
for applications are discouraged, So my question is what is the use case pg_cron
extension on DigitalOcean?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Hello @kaushalyapradeep
You’re correct,
pg_cron
can be used on the DigitalOcean managed Postgres service, but only on thedefaultdb
because thepostgresql.conf
file is not user-configurable in the managed service. Using thedefaultdb
is typically discouraged for applications for separation of concerns and better management.However,
pg_cron
can be quite useful in a number of scenarios like performing routine maintenance tasks (clean-up, vacuuming, etc.), running regular data analysis queries, generating reports, and more, all on a specified schedule.While it might not be ideal for all application scenarios due to the limitations you pointed out, it offers some handy automation capabilities within those parameters.
Hope that this helps!