Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name
Дата
Msg-id CAKJS1f9bAsZVodugqwAS6kSEtrOQKOEpdeBVJALR8iEZf9kHXg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name  (Michael Paquier <michael@paquier.xyz>)
Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name  (Arthur Zakirov <a.zakirov@postgrespro.ru>)
Список pgsql-bugs
Дерево обсуждения 
On Mon, 11 Feb 2019 at 11:39, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Hmm ... I'd not looked at this before, but now that I do, the new API
> for LookupFuncName seems mighty confused, or at least confusingly
> documented.  It's not clear what the combinations of the flags actually
> do, or why you'd want to use them.
>
> I wonder whether you'd be better off replacing the two bools with an
> enum, or something like that.

Okay. Here's a modified patch with the enum.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
Вложения

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: BUG #15609: synchronous_commit=off insert performance regressionwith secondary indexes
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15629: Typo in Documentation