-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to stop pg_cron scheduler #352
Comments
Can you try killing the process?
SELECT
pid as process_id,
usename as database_user,
application_name,
backend_start as when_process_began,
wait_event_type,
state,
query,
backend_type
FROM pg_stat_activity where application_name ilike 'pg_cron scheduler';
SELECT pg_terminate_backend(<pid of the process>) |
IIRC I tried to kill the backend postgres process, but it was then auto restarted, but I think I used a different query. |
Sorry, I forgot about this. I can successfully kill the cron process, but then a new one is spawned.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm unable to stop pg_cron scheduler, even after I drop the extension. I also tried to restart the cluster and whole postgres service, but the scheduler is still running.
This is an issue, because it maintains connection to the database. In the case I install the extension to database other than postgres, it effectively prevents me from dropping/renaming the database.
It happened both with background workers and libpq connection.
I'd expect that dropping the extension should stop the scheduler.
I'm running postgresql-16-cron 1.6.4-1.pgdg22.04+1
The text was updated successfully, but these errors were encountered: