Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables
Дата
Msg-id 3615.1249569418@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Kevin Grittner wrote:
>> Any idea whether domains are an issue?

> I don't believe that they are an issue. The issue arises only when a 
> catalog oid is used in the on-disk representation of a type. AFAIK the 
> on-disk representation of a domain is the same as its base type.

Arrays of domains would be a problem, if we had 'em, which we don't...

Also, as Peter already noted, arrays of built-in types are not really a
problem because the OID won't have changed since 8.3.  It's only arrays
of types created post-initdb that are risk factors.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Adding error message "source"
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: Re: [Pg-migrator-general] Composite types break pg_migrated tables