Date: Tue, 22 Nov 2022 16:28:10 -0500
From: Bruce Momjian <bruce@momjian.us>
To: robrwo@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: crosstab documentation should add a note about use in
 materialized views
Message-ID: <Y30+6uiZANO7iZkW@momjian.us>
References: 
 <166608181322.2042183.16156070469788658076@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <166608181322.2042183.16156070469788658076@wrigleys.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/Y30%2B6uiZANO7iZkW%40momjian.us>
Precedence: bulk

On Tue, Oct 18, 2022 at 08:30:13AM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/15/tablefunc.html
> Description:
> 
> When using a crosstab in a materialized view, if the SQL is not qualified
> with a schema, that restoring a database from a dump may fail. See the
> discussion in
> https://www.postgresql.org/message-id/16202-b6b345c9d2819409%40postgresql.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?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Indecision is a decision.  Inaction is an action.  Mark Batterson