Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: pgadmin-hackers-owner@postgresql.org
>>[mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of
>>Guillaume LELARGE
>>Sent: 13 December 2005 23:44
>>To: pgadmin-hackers@postgresql.org
>>Subject: Re: [pgadmin-hackers] Schema bug
>>
>>Le Mardi 13 Décembre 2005 00:48, Guillaume LELARGE a écrit :
>>
>>>Le Samedi 10 Décembre 2005 16:55, Andreas Pflug a écrit :
>>>
>>>>Dave Page wrote:
>>>>
>>>>>>I still think this patch should be applied.
>>>>>
>>>>>Does anyone see a reason /not/ to do this?
>>>>
>>>>Hm, Guillaume started a thread on pgsql-hackers about
>>
>>renaming system
>>
>>>>schemas in general, maybe we should wait for the result of that
>>>>discussion.
>>>
>>>Well, it seems that pg_* schemas are system schemas and
>>
>>that public and
>>
>>>information_schema schemas are public one. I think we
>>
>>should exclude system
>>
>>>schemas depending on their names and show public and
>>
>>information_schema,
>>
>>>whatever their actual name are.
>>>
>>>I can bring a new patch if you agree with this and if you
>>
>>find this useful.
>>
>>What about this one ?
>
>
> I don't have a problem with that. Anyone else?
I *do* have a problem if information_schema becomes non-system. For
pgsql-core this is non-system, but a user would consider this system and
like to have its display suppressed for day-to-day work.
I'm still not convinced we need to do anything. Renaming public is
highly irregular, and finally showing system objects will make it
reappear. The schema restriction allows individual filters who likes it.
Regards,
Andreas