Re: Lock conflict behavior?

Jeff Davis <pgsql@j-davis.com> writes:
> On Wed, 2009-01-21 at 15:08 -0800, Jeff Davis wrote:
>> If we keep the permission check in LockTableCommand(), I can make a
>> patch that produces a more useful error message when the table is
>> removed right before the pg_class_aclcheck().

> Attached.

This is pretty horrid, because it converts any error whatsoever into
"relation does not exist".  For counterexamples consider "statement
timeout reached", "query cancelled by user", "pg_class is corrupted",
etc etc.
        regards, tom lane