From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: robrwo@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: crosstab documentation should add a note about use in
 materialized views
In-reply-to: <Y30+6uiZANO7iZkW@momjian.us>
References: 
 <166608181322.2042183.16156070469788658076@wrigleys.postgresql.org>
 <Y30+6uiZANO7iZkW@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Tue, 22 Nov 2022 16:28:10 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3558400.1669152952.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 Nov 2022 16:35:52 -0500
Message-ID: <3558401.1669152952@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3558401.1669152952%40sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
>> When using a crosstab in a materialized view, if the SQL is not qualifi=
ed
>> with a schema, that restoring a database from a dump may fail. See the
>> discussion in
>> https://www.postgresql.org/message-id/16202-b6b345c9d2819409%40postgres=
ql.org

> I am trying to understand the scope of this breakage.  I think it is
> because crosstab specifies queries as strings, and a materialized view
> has to run the query during restore to populate the materialized view. =

> Is this the only combination of pg_dump restore breakage?

It doesn't sound like this is in any way unique to crosstab.
Any underqualified reference to a user-defined object can cause
problems during dump/restore, because of the restricted search_path
we use during restore.

			regards, tom lane