Re: (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17
Дата
Msg-id 823491.1739806456@sss.pgh.pa.us
обсуждение исходный текст
Ответ на (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17  (Kanitchet Vaiassava <kanichet@hotmail.com>)
Список pgsql-bugs
Дерево обсуждения 
Kanitchet Vaiassava <kanichet@hotmail.com> writes:
> Actual Behavior (postgres 17)
>   *   Calling the function directly works fine (search_path = public).
>   *   Calling the function through a Materialized View defaults search_path to pg_catalog, pg_temp, causing it to
failto find tables 

This is an intentional change in v17.

>   *   PostgreSQL’s security model in newer versions (15+) might enforce a stricter search_path default (pg_catalog,
pg_temp)inside Materialized View refresh execution ???? (which I have not found in web's document) 

It's the first compatibility issue listed in the v17 release notes:

https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-MIGRATION

            regards, tom lane

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