| From: | "Donald Fraser" <demolish(at)cwgsy(dot)net> |
|---|---|
| To: | "[BUGS]" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | pg_catalog |
| Date: | 2003-04-08 15:37:38 |
| Message-ID: | 005401c2fde4$cc5839a0$1664a8c0@DEMOLITION |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PostgreSQL v 7.3.2
Is there a reason why I can create in the SCHEMA pg_catalog the following object types?
1) Functions
2) Operators
3) Types
Yet I cannot create tables in the SCHEMA pg_catalog.
Hopefully there is a logical solution rather than a bug.
Before someone shoots me down with "What are you doing modifying system catalogues!".
The short answer is I need to be able specify whether a SCHEMA should get backed up or not, for exactly the same reasons why pg_catalog doesn't get backed up. Because pg_catalog does not get backed up, I tried to utilise this feature but I came across the problem of not being able to put tables in it.
Regards
Donald Fraser.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Norman Vine | 2003-04-08 20:49:11 | missing DLLIMPORT for cpu_index_tuple_cost |
| Previous Message | Stephan Szabo | 2003-04-08 14:48:16 | Re: Bug #938: Wrong UPDATE if exist INNER JOIN and alias |