Re: Deadlock with pg_dump? - Mailing list pgsql-hackers

From Chris Campbell
Subject Re: Deadlock with pg_dump?
Date
Msg-id 7B2C5768-D380-4EFC-98D9-D8B53B6CB1D0@bignerdranch.com
Whole thread Raw
In response to Re: Deadlock with pg_dump?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Oct 26, 2006, at 18:45, Tom Lane wrote:

> log_min_error_statement = error would at least get you the statements
> reporting the deadlocks, though not what they're conflicting against.

Would it be possible (in 8.3, say) to log the conflicting backend's  
current statement (from pg_stat_activity, perhaps)? I guess the  
conflicting backend would currently be waiting for a lock, so its  
current query (before releasing the lock) is the one we want.

Thanks!

- Chris



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Deadlock with pg_dump?
Next
From: "Gurjeet Singh"
Date:
Subject: bug in on_error_rollback !?