Re: Adding some error context for lock wait failures

From: Zhang Mingli <zmlpostgres(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Steve Baldwin <steve(dot)baldwin(at)gmail(dot)com>
Subject: Re: Adding some error context for lock wait failures
Date: 2025-07-11 04:03:46
Message-ID: 47aad542-4002-4421-800c-e9da832e3a40@Spark
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Jul 11, 2025 at 11:36 +0800, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, wrote:
>
> This seems to be quite useful to me, initially I thought if we can
> print the relation and database name then this could be even better
> but it might be a bad idea to fetch the object name while we are in
> error callback.
May be confused if there were tables with same names under different schemas.

--
Zhang Mingli
HashData

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-07-11 04:19:49 Re: Adding some error context for lock wait failures
Previous Message Tom Lane 2025-07-11 03:48:20 Re: A recent message added to pg_upgade