Re: pg_class and enum types
| От | Tom Lane |
|---|---|
| Тема | Re: pg_class and enum types |
| Дата | |
| Msg-id | 11565.1243200585@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: pg_class and enum types (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: pg_class and enum types
|
| Список | pgsql-hackers |
Andrew Dunstan <andrew@dunslane.net> 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
В списке pgsql-hackers по дате отправления: