Skip site navigation (1) Skip section navigation (2)

Re: Deadlock with pg_dump?

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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


In response to

pgsql-hackers by date

Next:From: Carl NordenDate: 2006-10-27 02:13:10
Subject: Build of postgresql 8.2 beta 2 failure
Previous:From: Alvaro HerreraDate: 2006-10-26 23:23:12
Subject: Re: Deadlock with pg_dump?

pgsql-patches by date

Next:From: Jaime CasanovaDate: 2006-10-27 04:42:17
Subject: Re: Tablespace for temporary objects and sort files
Previous:From: Alvaro HerreraDate: 2006-10-26 23:23:12
Subject: Re: Deadlock with pg_dump?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group