Re: [HACKERS] fresh regression - regproc result contains unwanted schema

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: [HACKERS] fresh regression - regproc result contains unwanted schema
Дата
Msg-id CAFj8pRDE9MS3PnxpjcpK9npmweNgO6aRYOUBymVsBFrNVnGZAQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] fresh regression - regproc result contains unwanted schema  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers


2017-10-14 17:26 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> When function is overwritten, then regproc result contains schema, although
> it is on search_path

There's no "fresh regression" here, it's done that more or less since
we invented schemas.  See regprocout:

             * Would this proc be found (uniquely!) by regprocin? If not,
             * qualify it.

git blame dates that comment to commit 52200bef of 2002-04-25.

Admittedly, qualifying the name might not be sufficient to disambiguate,
but regprocout doesn't have any other tool in its toolbox, so it uses
the hammer it's got.  If you're overloading functions, you really need
to use regprocedure not regproc.

It is false alarm. I am sorry. I shot by self. Thank you for explanation

Nice evening.

Pavel


                        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] fresh regression - regproc result contains unwanted schema
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] pg_control_recovery() return value when not in recovery