Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.
Дата
Msg-id 19074.1459356346@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [postgresSQL] [bug] Two or more different types of constraints with same name creates ambiguity while drooping.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Tom Lane wrote:
>> What we need is a unique index on pg_constraint.
>> The problem with that is that pg_constraint contains both table-related
>> and type (domain) related constraints; but it strikes me that we could
>> probably create a unique index on (conrelid, contypid, conname).

> Weren't you proposing elsewhere to split pg_constraint in two catalogs,
> one for table constraint and another for domain constraints?  That seems
> a cleaner solution to me.

Yeah, and you'll notice how much progress we've made towards that.
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: snapshot too old, configured by time
Следующее
От: Amit Langote
Дата:
Сообщение: Re: [GENERAL] pg_restore casts check constraints differently