Re: BUG #16202: Cannot restore database that has materialized viewusing crosstab (tablefunc) - Mailing list pgsql-bugs

From Wagner Engel
Subject Re: BUG #16202: Cannot restore database that has materialized viewusing crosstab (tablefunc)
Date
Msg-id CANV-=J=1zv7cyZU=OcUpb6vCQWTTRJjy6MA6MgvpO-d1cEqAtg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16202: Cannot restore database that has materialized view using crosstab (tablefunc)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Indeed, that was it. Thank you so much!


Em sex., 10 de jan. de 2020 às 15:04, Tom Lane <tgl@sss.pgh.pa.us> escreveu:
PG Bug reporting form <noreply@postgresql.org> writes:
> If I build a materizalized view that uses the crosstab() function, a
> dump/restore cycle will not restore the database.

> CREATE VIEW v AS
> SELECT * FROM crosstab (
>       'SELECT id FROM t as t1',
>       'SELECT id FROM t as t2'
> ) ct (a integer, b integer);

This view is unsafe because it doesn't schema-qualify its reference
to table t.  It will fail if run with a restrictive search_path,
which is what pg_dump does for security reasons.

An ordinary view reference to "t" would be all right, because the
system understands what that is and can adjust the schema qualification;
but here you've just got a string that happens to contain "t" in it.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16202: Cannot restore database that has materialized view using crosstab (tablefunc)
Next
From: PG Bug reporting form
Date:
Subject: BUG #16203: So difficult to set an use postgres