Re: Lock conflict behavior?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Lock conflict behavior?
Date: 2009-01-22 06:18:58
Message-ID: 1232605138.31863.8.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
Jeff Davis

Attachment Content-Type Size
lock_error.patch text/x-patch 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-01-22 07:12:13 Re: Pluggable Indexes (was Re: rmgr hooks (v2))
Previous Message Pavel Stehule 2009-01-22 05:37:37 Re: plpgsql: numeric assignment to an integer variable errors out