Re: CREATE INDEX regression in 17 RC1 or expected behavior?

From: Tom Dunstan <tom(at)tomd(dot)cc>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: CREATE INDEX regression in 17 RC1 or expected behavior?
Date: 2024-09-26 03:12:55
Message-ID: CAPPfruxsMOTkyQjT3S8u6Jj=+hFD7xOaH1ivJijTn_ZRLdSuJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 26 Sept 2024 at 12:22, Tom Dunstan <pgsql(at)tomd(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-09-26 03:16:06 Re: CREATE INDEX regression in 17 RC1 or expected behavior?
Previous Message Tom Dunstan 2024-09-26 02:52:32 CREATE INDEX regression in 17 RC1 or expected behavior?