834-Adding-pg_cron-to-Postgres-Docker-Image #842
No reviewers
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!842
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "834-Adding-pg_cron-to-Postgres-Docker-Image"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What's been done
Done on Windows 11
Added pg_cron to our postgres image. Uses citusdata's pg_cron git. Citusdata is the industry standard, and has been acquired by Microsoft. If we ever switch of using an Alpine image, this could be changed to not require its own Dockerfile.
How to check if it works
IMPORTANT
Make sure that you delete existing postgres image and volumes
4.1. You should see one row containing pg_cron
5.1. You should see cron
I had some problems with the volumes, so if you have the time, prune docker. It should work with just removing volumes using docker compose down -v.
Review on #842
Whats done
Tested on macOS
Inspected following files
compose.yaml
DockerCompose/postgres_dockerfile/Dockerfile
+ Follows standard
DockerCompose/init_sql/01-sensors.sql
+ Follows standard
DockerCompose/init_sql/03-sensors_cron_jobs.sql
+ Follows standard
What needs to be done
Conclusion