Re: Cache lookup errors with functions manipulation object addresses

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Cache lookup errors with functions manipulation object addresses
Дата
Msg-id 20180514222457.GA1600@paquier.xyz
обсуждение исходный текст
Ответ на Re: Cache lookup errors with functions manipulation object addresses  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Cache lookup errors with functions manipulation object addresses  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On Mon, May 14, 2018 at 04:27:48PM -0400, Alvaro Herrera wrote:
> I think we're better off adding a new function and avoid changing the
> signature of GetForeignServer et al.  Or maybe rename the function and
> keep the original name as a compatibility wrapper macro.

On the other hand, if we make the change visible because of a
compilation failures, then modules would become aware of the problem and
react?  I would not expect modules to set missing_ok to true anyway as
they expect those objects to exist, so I can live with a new function.
What about naming those GetForeignServerExtended and
GetForeignDataWrapperExtended?
--
Michael

Вложения

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Postgres 11 release notes
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Cache lookup errors with functions manipulation object addresses