Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?) - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)
Date
Msg-id 28694.1382366865@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)  (Ken Tanzer <ken.tanzer@gmail.com>)
Responses Re: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)
List pgsql-general
Tree view 
Ken Tanzer <ken.tanzer@gmail.com> writes:
> When trying to move a database from 8.3 to 9.2.5, the plain text pg_dump
> did not restore without errors.  (I used pg_dump from 9.2.5)  The problem
> seems to relate to references to other schemas and the schema search paths.

What this looks like to me is that you have a SQL function which isn't
protecting itself against changes in search_path.  It could fail in any
context where somebody's changed search_path, not just a restore run.
You should consider fully qualifying the table reference in the function's
source code, or adding a "SET search_path" clause to the function
definition.

            regards, tom lane

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)
Next
From: "Ben"
Date:
Subject: pg_dump resulting in excessive memory use by postmaster process