Re: Adding some error context for lock wait failures - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Adding some error context for lock wait failures
Date
Msg-id 2463552.1756496793@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding some error context for lock wait failures  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Dilip Kumar <dilipbalaut@gmail.com> writes:
> On Fri, Jul 11, 2025 at 9:34 AM Zhang Mingli <zmlpostgres@gmail.com> wrote:
>> May be confused if there were tables with same names under different schemas.

> If that's the only issue we can print schema qualified name, but I
> think the problem is in error callback we just have lock tag
> information which only have OIDs and we don't look up the
> relcaches/sys table from the error path.

Yeah.  In an ideal world we'd look up the OID references and print
the object names.  But trying to do catalog lookups in an
already-failed transaction seems way too dangerous, just as we've
judged it to be for deadlock reports.

Hearing no comments beyond that one, pushed.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Assert single row returning SQL-standard functions
Next
From: "Joel Jacobson"
Date:
Subject: Re: Assert single row returning SQL-standard functions