| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Lock conflict behavior? |
| Date: | 2009-01-22 23:27:59 |
| Message-ID: | 1232666879.3578.197.camel@dell.linuxdev.us.dell.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2009-01-22 at 18:20 -0500, Tom Lane wrote:
> Jeff Davis <pgsql(at)j-davis(dot)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.
Ah, I see. Well, I guess there's not a better way to handle that error
after all. There's no way to tell what exception you're catching
specifically, right?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-01-22 23:45:57 | Re: Pluggable Indexes |
| Previous Message | Tom Lane | 2009-01-22 23:27:47 | Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows. |