Re: CREATE INDEX regression in 17 RC1 or expected behavior? - Mailing list pgsql-hackers

From Tom Dunstan
Subject Re: CREATE INDEX regression in 17 RC1 or expected behavior?
Date
Msg-id CAPPfruxsMOTkyQjT3S8u6Jj=+hFD7xOaH1ivJijTn_ZRLdSuJg@mail.gmail.com
Whole thread Raw
In response to CREATE INDEX regression in 17 RC1 or expected behavior?  (Tom Dunstan <pgsql@tomd.cc>)
List pgsql-hackers
On Thu, 26 Sept 2024 at 12:22, Tom Dunstan <pgsql@tomd.cc> wrote:
I presume that this is related to the work in 17 around using restricted search paths in more places, but it's just a guess. CREATE INDEX isn't mentioned in the release notes.

Reading a bit closer yields:

> Functions used by expression indexes and materialized views that need to reference non-default schemas must specify a search path during function creation.

So I guess that makes this an intended breakage.

It might help to add CREATE INDEX (and maybe CREATE MATERIALIZED VIEW if that's also affected) to the list of commands affected in the release notes to make this more obvious - having a list of commands that are affected that didn't include it made me think that this wasn't intended.

Cheers

Tom

pgsql-hackers by date:

Previous
From: Tom Dunstan
Date:
Subject: CREATE INDEX regression in 17 RC1 or expected behavior?
Next
From: Nathan Bossart
Date:
Subject: Re: CREATE INDEX regression in 17 RC1 or expected behavior?