deepaksood619 commented on PR #19842:
URL: https://github.com/apache/airflow/pull/19842#issuecomment-2135987429

   Yes this is happening again for us too.
   
   ```bash
   airflow-postgresql-0 postgresql 2024-05-29T01:12:13.163792559+05:30 
2024-05-28 19:42:13.163 GMT [4019479] ERROR:  could not obtain lock on row in 
relation "dag_run"
   
   airflow-postgresql-0 postgresql 2024-05-29T01:12:13.163834190+05:30 
2024-05-28 19:42:13.163 GMT [4019479] STATEMENT:  SELECT dag_run.state AS 
dag_run_state, dag_run.id AS dag_run_id, dag_run.dag_id AS dag_run_dag_id, 
dag_run.queued_at AS dag_run_queued_at, dag_run.execution_date AS 
dag_run_execution_date, dag_run.start_date AS dag_run_start_date, 
dag_run.end_date AS dag_run_end_date, dag_run.run_id AS dag_run_run_id, 
dag_run.creating_job_id AS dag_run_creating_job_id, dag_run.external_trigger AS 
dag_run_external_trigger, dag_run.run_type AS dag_run_run_type, dag_run.conf AS 
dag_run_conf, dag_run.data_interval_start AS dag_run_data_interval_start, 
dag_run.data_interval_end AS dag_run_data_interval_end, 
dag_run.last_scheduling_decision AS dag_run_last_scheduling_decision, 
dag_run.dag_hash AS dag_run_dag_hash, dag_run.log_template_id AS 
dag_run_log_template_id, dag_run.updated_at AS dag_run_updated_at, 
dag_run.clear_number AS dag_run_clear_number
   
   airflow-postgresql-0 postgresql 2024-05-29T01:12:13.163839590+05:30  FROM 
dag_run
   
   airflow-postgresql-0 postgresql 2024-05-29T01:12:13.163844440+05:30  WHERE 
dag_run.dag_id = 'xxx' AND dag_run.run_id = 
'scheduled__2024-05-28T19:41:00+00:00' FOR UPDATE NOWAIT
   ```
   
   This is also being resolved automatically in some time, and coming 
intermittently.
   
   Any help would be deeply appreciated.
   
   Thanks in advance!!


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to