ERRCODE_T_R_DEADLOCK_DETECTED - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject ERRCODE_T_R_DEADLOCK_DETECTED
Date
Msg-id 20150319.120512.1245040145464332230.t-ishii@sraoss.co.jp
Whole thread Raw
Responses Re: ERRCODE_T_R_DEADLOCK_DETECTED  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
The error code is used in two places:
ereport(ERROR,        (errcode(ERRCODE_T_R_DEADLOCK_DETECTED),         errmsg("canceling statement due to conflict with
recovery"),  errdetail("User transaction caused buffer deadlock with recovery.")));
 
ereport(ERROR,        (errcode(ERRCODE_T_R_DEADLOCK_DETECTED),         errmsg("deadlock detected"),
errdetail_internal("%s",clientbuf.data),         errdetail_log("%s", logbuf.data),         errhint("See server log for
querydetails.")));
 

The latter is a normal deadlock and can be obseved by stats because
pgstat_report_deadlock() is called.

The former is using the same error code but the meaning is pretty
different and users might be confused IMO.

I am not sure sharing the same error code is the best idea here.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Parallel Seq Scan
Next
From: Devrim Gündüz
Date:
Subject: Help needed for PL/Ruby