citusdata / citusdata/pg_cron

schedule_in_database function wastes sequence values

Open
#358 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
3.9k
Forks
260
Avg merge
5d 5h
Merged PRs (30d)
1

Description

I'm setting up some pg_cron jobs using Ansible, and was hoping to just call the `schedule_in_database` function on each deployment, as this will not create a job that already exists. However, I discovered that it does consume a value from the `jobid_seq` sequence even when it does not insert a new row, which is suboptimal as that will mean that my deployment scripts burn through a lot of sequence values unnecessarily. The column is a 64-bit integer which seems really overkill but should prevent this from becoming an actual problem in practice, but it would still be nice if it didn't consume sequence values unnecessarily.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.