Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Logging conflicted queries on deadlocks
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Logging conflicted queries on deadlocks
- Date: Thu, 28 Feb 2008 10:34:27 -0300
ITAGAKI Takahiro wrote: > There are some open issues. One of the issues is that the killed query is > logged by log_min_error_statement, but conflicted query is logged in DETAIL. > Killed query is logged only on server but conflicted queries are > sent to both server and client. In addition, if log_min_error_statement > is less than ERROR level, only the conflicted queries are logged. > -- it's inconsistent and unsymmetric. Hm, your patches crashes for me when there are 3 sessions deadlocked. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
- References:
- Logging conflicted queries on deadlocks
- From: ITAGAKI Takahiro
- Logging conflicted queries on deadlocks
- Prev by Date: Silly Newbie question
- Next by Date: Re: Buildfarm member gypsy_moth seems not to like alignment patch
- Previous by thread: Re: Logging conflicted queries on deadlocks
- Next by thread: CREATE TABLE, load and freezing
- Indexes: