Re: pg_class and enum types

Поиск
Список
Период
Сортировка
Искать
От
Gevik Babakhani
Тема
Re: pg_class and enum types
Дата
в 19:18:10
Msg-id
4A19C77F.6010700@xs4all.nl
Ответ на
Список
Дерево обсуждения
pg_class and enum types Gevik Babakhani <pgdev@xs4all.nl>
Re: pg_class and enum types Andrew Dunstan <andrew@dunslane.net>
Re: pg_class and enum types Gevik Babakhani <pgdev@xs4all.nl>
Re: pg_class and enum types Robert Haas <robertmhaas@gmail.com>
Re: pg_class and enum types Gevik Babakhani <pgdev@xs4all.nl>
Re: pg_class and enum types Andrew Dunstan <andrew@dunslane.net>
Re: pg_class and enum types Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_class and enum types Gevik Babakhani <pgdev@xs4all.nl>
Tom Lane wrote:
> Andrew Dunstan  writes:
>   
>> Gevik Babakhani wrote:
>>     
>>> select * from pg_class where relname='test_type'
>>>       
>
>   
>> It's not so much that enum types are handled specially, but that 
>> composite types are. :-)
>>     
>
> Relations (tables) have always had both pg_class and pg_type entries.
> The pg_class entry denotes the relation proper, the pg_type entry
> denotes the relation's rowtype.
>
> Composite types have the same two entries, there's just a different
> notion of which one is primary.
>
> (The reason a composite type has to have a pg_class entry is that
> it has pg_attribute entries, and those have to have something in
> pg_class for their attrelid to link to.)
>
> 			regards, tom lane
>
>   
Thank you :)

-- 
Regards,
Gevik


В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата:
От: Tom Lane
Дата:
FAQ