[New Extension]: pg_cron

[ardentperf]

Is there an existing issue for this extension request?

• I have searched for an existing issue, and could not find a duplicate request.

Extension Name

pg_cron

Project Repository URL

https://github.com/citusdata/pg_cron

Extension Website URL (Optional)

No response

Short Description

pg_cron is a simple cron-based job scheduler for Postgres that runs inside the database as an extension.

Main LICENSE Link

PostgreSQL License

https://github.com/citusdata/pg_cron/blob/main/LICENSE

License Compliance

• The extension's license (linked above) complies with the list of allowed licenses.

Known Dependent Extensions

None

Component Owner and Maintenance Commitment

• I/My organization commit to becoming the Component Owner and maintaining the extension image in the future.

Additional Notes (Optional)

No response

GitHub Handles of Component Owners

ardentperf

Code of Conduct

• I agree to follow this project's Code of Conduct

[ardentperf]

In the process of working on this, it seems that the current scaffolding doesn't handle the case where the SQL extension is a minor version (1.6) and the package is a patch version (1.6.7).

Two issues:

1. e2e test infra autofills package version if create_extension = true. i will create the initial PR with create_extension=false so that tests pass. separately I'll submit a PR to have E2E tests create the default extension version, which seems the easiest way around this. We can discuss on the PR if that approach is desired; if so then I can update this extension after that PR is committed.
2. renovate README custom manager only supports package version. if the SQL version is different then we can't update with renovate. same solution - will just exclude version from README example (the version is optional).

[GabriFedi97]

@ardentperf thanks for reporting this.
I proposed a PR (#149) to add the ability to explicitly specify the SQL extension version in the metadata.hcl file, so it can be reused during e2e tests.
However, I realized it may not be sufficient to have e2e passing for pg_cron. Since in e2e we are forcing the extension to be created in the app database, pg_cron throws an error saying it requires to be created in the same database defined by the cron.database_name value. That value is defaulted to postgres and we currently have no way to change it.
I opened #153 to address this.

[ardentperf]

@GabriFedi97 yep, this was covered in the README.md examples

I did manually run all the steps in the README and schedule some jobs and verify that the extension works, using my local e2e test environment after running e2e tests with create_extension=false. Do you think the other two PRs will be merged soon? If not, should we add this extension initially with create_extension=false? I’m happy to update it as soon as the other two PRs are merged

[GabriFedi97]

@ardentperf I believe we should wait for #153 and #154 to be merged first and rebase #143 accordingly. Unfortunately, I expect some delays this week due to Kubecon EU.

[GabriFedi97]

@ardentperf the two PRs have been merged. Feel free to rebase #143 and to submit it for review.