Re: BUG #12465: Materialized view dump restoration issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jeff(dot)casavant(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #12465: Materialized view dump restoration issue
Date: 2015-01-09 20:42:22
Message-ID: 12297.1420836142@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

jeff(dot)casavant(at)gmail(dot)com writes:
> Code to reproduce:

> create function b() returns int as $$ select 1 $$ language sql;
> create function a() returns int as $$ select b() $$ language sql;
> create schema qwr;
> create materialized view qwr.c as select a();

This is not a pg_dump bug, this is a broken definition of function a().
That function will fail in any context where the caller changes
search_path, not only pg_dump. You can perhaps get away without that
in a single-schema database, but not with multiple schemas.

You could fix it by schema-qualifying b in the text of a,
or by adding a "SET schema_path" clause to a.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jefferson Casavant 2015-01-09 20:48:17 Re: BUG #12465: Materialized view dump restoration issue
Previous Message Kevin Grittner 2015-01-09 19:09:31 Re: BUG #12469: pg_locks shows locks held by pids not found i n pg_stat_activity or ps