Message-ID: <c9ad7d70d6e60acf4cc2dce4c065f6849368ad6c.camel@cybertec.at>
Subject: Re: Error creating materialized view
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Shaun Robinson <srobinson@mdxperience.com>, 
	pgsql-general@lists.postgresql.org
Date: Mon, 25 Nov 2024 13:54:45 +0100
In-Reply-To: <CAMJoR-Zv-otrJE4Wejs9us5x3gf-LBMfL0XT4UfZym-abx-j8w@mail.gmail.com>
References: 
	<CAMJoR-Zv-otrJE4Wejs9us5x3gf-LBMfL0XT4UfZym-abx-j8w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.52.4 (3.52.4-2.fc40) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/c9ad7d70d6e60acf4cc2dce4c065f6849368ad6c.camel%40cybertec.at>
Precedence: bulk

On Mon, 2024-11-25 at 06:08 +0000, Shaun Robinson wrote:
> I'm currently testing an application with Postgres 17.2 and am getting an=
 error
> when creating a=C2=A0materialized view which works in version 16 and belo=
w. The sql
> works fine running as a query, but adding the create=C2=A0materialized vi=
ew breaks it.
>=20
> The error comes when calling a custom function and the error is that a re=
lation
> doesn't exist (which it does as it works within the same query when not c=
reating
> a view).
>=20
> Is this a known issue in the version 17.2?

That's a deliberate improvemen; see the first point in
https://www.postgresql.org/docs/current/release-17.html#RELEASE-17-MIGRATIO=
N

you will have to schema-qualify all tables in the function or set the
"search_path" on the function.

Yours,
Laurenz Albe