Busted(?) optimization in ATAddForeignKeyConstraint

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Busted(?) optimization in ATAddForeignKeyConstraint
Дата
Msg-id 20849.1579817517@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: Busted(?) optimization in ATAddForeignKeyConstraint  (Thomas Munro <thomas.munro@gmail.com>)
Re: Busted(?) optimization in ATAddForeignKeyConstraint  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
I happened to notice this comment in the logic in
ATAddForeignKeyConstraint that tries to decide if it can skip
revalidating a foreign-key constraint after a DDL change:

             * Since we require that all collations share the same notion of
             * equality (which they do, because texteq reduces to bitwise
             * equality), we don't compare collation here.

Hasn't this been broken by the introduction of nondeterministic
collations?

            regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Allow to_date() and to_timestamp() to accept localized names
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: Busted(?) optimization in ATAddForeignKeyConstraint