You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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';
IIRC I tried to kill the backend postgres process, but it was then auto restarted, but I think I used a different query.
I'm not able to check it now, but I will try to check it in few days.
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: