Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID
Дата
Msg-id 20190612023656.GA1745@paquier.xyz
обсуждение исходный текст
Ответ на Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID  (Daniel Gustafsson <daniel@yesql.se>)
Список pgsql-bugs
On Tue, Jun 11, 2019 at 09:32:55AM -0400, Alvaro Herrera wrote:
> Yeah, looks better.  I think the error message should be a normal elog()
> cache failure, though ... at least in the COMMENT case, the obj-does-not-
> exist message is supposed to be thrown by get_object_address(), before
> check_object_ownership is called.
>
> As a matter of style, I would get rid of the 'conoid' variable and just
> use address.objectId where needed.

OK.  I have included both your comments, and committed the patch down
to 9.5 where it applies.  Thanks for the feedback!

s/unathorized/unauthorized/ by the way.
--
Michael

Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #15835: Errors altering data type of the column used in partial exclusion constraint
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #15833: defining a comment on a domain constraint fails withwrong OID