On Wed, 25 Sep 2024 22:16:06 -0500 Nathan Bossart <nathandboss...@gmail.com> wrote:
> On Thu, Sep 26, 2024 at 12:22:32PM +0930, Tom Dunstan wrote: > > Reporting in case this is unexpected. At the very least if a function used > > in an index must now always find other functions using an explicit path, it > > seems like this should be documented and noted in the release notes. > > The first compatibility entry in the release notes [0] has the following > sentence: > > Functions used by expression indexes and materialized views that need > to reference non-default schemas must specify a search path during > function creation. Also, this is documented as followins in https://www.postgresql.org/docs/17/sql-createindex.html . While CREATE INDEX is running, the search_path is temporarily changed to pg_catalog, pg_temp. By the way, this is not mentioned in CREATE MATERIALIZED VIEW documentation, although we can find in REFRESH MATERIALIZED VIEW doc. So, I sent the doc patch in [1], and create a commitfest entry [2]. [1] https://www.postgresql.org/message-id/20240805160502.d2a4975802a832b1e04afb80%40sraoss.co.jp [2] https://commitfest.postgresql.org/49/5182/ Regards, Yugo Nagata -- Yugo Nagata <nag...@sraoss.co.jp>
