| From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
|---|---|
| To: | "Decibel!" <decibel(at)decibel(dot)org> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: public.pg_class isn't a catalog table |
| Date: | 2007-09-06 04:35:58 |
| Message-ID: | 46DF83AE.60203@timbira.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers pgsql-bugs |
Decibel! wrote:
> Version 1.6.3; if you have a table in public called pg_class and try to
> drop it, pgAdmin gives an error:
>
> ERROR: permission denied: "pg_class" is a system catalog
>
That's because pgAdmin is issuing "DROP TABLE pg_class" instead of "DROP
TABLE public.pg_class". By the way, is there any reason for not using
the namespace?
I don't know if it's the best way but this little proof of concept fix
might be applied to all objects that can be created inside a schema. I
could provide I patch if you want it.
--
Euler Taveira de Oliveira
http://www.timbira.com/
| Attachment | Content-Type | Size |
|---|---|---|
| x.diff | text/x-patch | 730 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2007-09-06 06:23:46 | Re: public.pg_class isn't a catalog table |
| Previous Message | Decibel! | 2007-09-05 21:14:10 | Re: Maintenance on indexes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2007-09-06 06:23:46 | Re: public.pg_class isn't a catalog table |
| Previous Message | Decibel! | 2007-09-05 17:33:03 | public.pg_class isn't a catalog table |