MIME-Version: 1.0
From: Shaun Robinson <srobinson@mdxperience.com>
Date: Mon, 25 Nov 2024 06:08:16 +0000
Message-ID: <CAMJoR-Zv-otrJE4Wejs9us5x3gf-LBMfL0XT4UfZym-abx-j8w@mail.gmail.com>
Subject: Error creating materialized view
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000009860f20627b68f33"
Archived-At: <https://www.postgresql.org/message-id/CAMJoR-Zv-otrJE4Wejs9us5x3gf-LBMfL0XT4UfZym-abx-j8w%40mail.gmail.com>
Precedence: bulk

--0000000000009860f20627b68f33
Content-Type: text/plain; charset="UTF-8"

Hi,

I'm currently testing an application with Postgres 17.2 and am getting an
error when creating a materialized view which works in version 16 and
below. The sql works fine running as a query, but adding the
create materialized view breaks it.

The error comes when calling a custom function and the error is that a
relation doesn't exist (which it does as it works within the same query
when not creating a view).

Is this a known issue in the version 17.2?

Thanks
Shaun

--0000000000009860f20627b68f33
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;m currently testing an applic=
ation with Postgres 17.2 and am getting an error when creating a=C2=A0mater=
ialized view which works in version 16 and below. The sql works fine runnin=
g as a query, but adding the create=C2=A0materialized view breaks it.</div>=
<div><br></div><div>The error comes when calling a custom function and the =
error is that a relation doesn&#39;t exist (which it does as it works withi=
n the same query when not creating a view).</div><div><br></div><div>Is thi=
s a known issue in the version 17.2?</div><div><br></div><div>Thanks</div><=
div>Shaun</div></div>

--0000000000009860f20627b68f33--