Re: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges
От | Christoph Berg |
---|---|
Тема | Re: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges |
Дата | |
Msg-id | ZTfL1G1fBPQHVPWV@msg.df7cb.de обсуждение исходный текст |
Ответ на | Re: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges (Tommy Pavlicek <tommypav122@gmail.com>) |
Ответы |
Re: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges
Re: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges |
Список | pgsql-hackers |
Re: Tommy Pavlicek > I've added another patch (0002-require_unused_neg_com-v1.patch) that > prevents using a commutator or negator that's already part of a pair. Hmm. I agree with the general idea of adding sanity checks, but this might be overzealous: This change is breaking pgsphere which has <@ @> operator pairs, but for historical reasons also includes alternative spellings of these operators (both called @ with swapped operand types) which now explodes because we can't add them with the "proper" commutator and negators declared (which point to the canonical <@ @> !<@ !@> operators). https://github.com/postgrespro/pgsphere/blob/master/pgs_moc_compat.sql.in We might be able to simply delete the @ operators, but doesn't this new check break the general possibility to have more than one spelling for the same operator? Christoph
В списке pgsql-hackers по дате отправления: