Re: [I] psycopg2.errors.ObjectInUse: cannot ALTER TABLE "slices" because it is being used by active queries in this session [superset]

["mdeshmu (via GitHub)" <gi...@apache.org>]

mdeshmu commented on issue #25335:
URL: https://github.com/apache/superset/issues/25335#issuecomment-1765541637

   maybe there is a running query that has already locked your table and that's why your migration is stuck
   
   SELECT
     activity.pid,
     activity.usename,
     activity.query,
     blocking.pid AS blocking_id,
     blocking.query AS blocking_query
    FROM pg_stat_activity AS activity
    JOIN pg_stat_activity AS blocking ON blocking.pid = ANY(pg_blocking_pids(activity.pid));
   
   Analyze the output of this query to identify blocking queries
   You will see one migration-related query blocked by another query (likely not a migration query) that ran before it
   Kill non-migration-related query to unblock your migration https://linuxhint.com/postgres-kill-query-pid/


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org