Re: Two constraints with the same name not always allowed

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: Two constraints with the same name not always allowed
Дата
Msg-id 20180902170511.ibjquzhymvnfvkqs@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: Two constraints with the same name not always allowed  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Two constraints with the same name not always allowed
Список pgsql-bugs
On 2018-Sep-02, Tom Lane wrote:

> This also points up the lack of a suitable unique index on pg_constraint.
> It's sort of difficult to figure out what that should look like given that
> pg_constraint contains two quasi-independent collections of constraints,
> but maybe UNIQUE(conrelid,contypid,conname) would serve given the
> reasonable assumption that exactly one of conrelid and contypid is zero.

Hmm ... c.f. 7eca575d1c28.  Maybe we should split them out?  Are there
reasons to have them together at all?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Two constraints with the same name not always allowed
Следующее
От: Andres Freund
Дата:
Сообщение: Re: BUG #15350: Getting invalid cache ID: 11 Errors