| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: information_schema OID |
| Date: | 2003-05-07 01:51:12 |
| Message-ID: | 074701c3143b5dc64000a8c0@fhp.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As information_schema has found its way into the initdb script, it can
> be considered a system schema. Unfortunately, it has an arbitrary OID,
> so pgadmin3 will not detect it as system schema.
> How should pgadmin3 handle this? Will information_schema eventually get
> a dedicated OID or should we check for the name?
Also, should the information_schema be pinned so that it cannot be dropped?
This would help db admin projects such as phpPgAdmin be able to rely on
information_schema being there...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yuezh | 2003-05-07 02:38:40 | about updating view |
| Previous Message | Christopher Kings-Lynne | 2003-05-07 01:50:15 | Re: 7.4 features list |