| From: | Chris Campbell <chris(at)bignerdranch(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deadlock with pg_dump? |
| Date: | 2006-10-27 00:27:31 |
| Message-ID: | 7B2C5768-D380-4EFC-98D9-D8B53B6CB1D0@bignerdranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carl Norden | 2006-10-27 02:13:10 | Build of postgresql 8.2 beta 2 failure |
| Previous Message | Alvaro Herrera | 2006-10-26 23:23:12 | Re: Deadlock with pg_dump? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2006-10-27 04:42:17 | Re: Tablespace for temporary objects and sort files |
| Previous Message | Alvaro Herrera | 2006-10-26 23:23:12 | Re: Deadlock with pg_dump? |