Repository Issue Activity (beta)

#7 Add a way to run jobs once at a particular time

#366 FR: Add a per-schedule option to disable logging runs

#432 1.6.7 fails to build against PostgreSQL 19 beta 1

#426 ERROR: unrecognized configuration parameter "cron.database_name"

#323 installation on windows

#22 how to install pg_cron in Windows 10

#434 cron.unschedule(integer) is ambiguous on EDB Postgres Advanced Server (EPAS) 18

#423 Cannot load pg_cron in Postgres 18 Fedora 43

#397 Massive memory usage in 1.6.4

#427 pg_cron: cron.database_name does not support multiple databases

#422 Prisma Next Extension

#48 Not able to make pg_cron work

#419 Scheduling job to regard DOM && DOW.

#424 Q: "Must be superuser to create this extension."

#416 Improve run history management for high-frequency jobs

#333 [BUG] setting search_path causes error

#415 Segmentation fault in version 1.6.7

#408 Index on the `cron.job_run_details` table

#63 pg_cron hangs when cron.max_running_jobs is exceeded

#325 on Google Cloud Platform Cloud SQL pg_cron is not working on monthly and weekly schedule

#89 Multiple database

#400 cron.job_run_details incorrectly logs 1 row. instead of function's RETURN value

#410 Update CHANGELOG for pg_cron v1.6.7 and v1.6.6 is not showing in latest tag v1.6.7

#352 Unable to stop pg_cron scheduler

#407 Is it possible to do internal transaction control using a stored procedure scheduled with pg_cron?