| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | robrwo(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: crosstab documentation should add a note about use in materialized views |
| Date: | 2022-11-22 21:35:52 |
| Message-ID: | 3558401.1669152952@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> 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?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2022-11-23 02:44:49 | Re: Logical replication missing information |
| Previous Message | Bruce Momjian | 2022-11-22 21:28:10 | Re: crosstab documentation should add a note about use in materialized views |