Postgres Pro
Downloads
Home   >   mailing lists

Re: (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17
Date
Msg-id 823491.1739806456@sss.pgh.pa.us
Whole thread Raw
In response to (Bug? or Intended?) Inconsistent search_path Behavior in Function Calls via Materialized View in PostgreSQL 17  (Kanitchet Vaiassava <kanichet@hotmail.com>)
List pgsql-bugs
Tree view 
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 by date:

Previous
From: Tom Lane
Date:
Subject: Re: issue with PSQL 17.1 on Suse 15 Linux SP6
Next
From: Andrew Dunstan
Date:
Subject: Re: BUG #18816: pg16 requires perl 5.14+ but is not documented