[BUGS] pg_dump does not fully include the schema, causing runtime errors - Mailing list pgsql-bugs

From Ian R. Campbell
Subject [BUGS] pg_dump does not fully include the schema, causing runtime errors
Date
Msg-id CAOC8YUcUJJywOjBsutUOtg9fQY7Wmg2veKKdLK6Cm8jKVyAcjQ@mail.gmail.com
Whole thread Raw
Responses Re: [BUGS] pg_dump does not fully include the schema, causing runtime errors
Re: [BUGS] pg_dump does not fully include the schema, causingruntime errors
List pgsql-bugs
pg_dump uses SET search_path in order to simplify schema references. Below is a snippet of a CREATE TABLE definition that references a function in the 'internal' schema:

...    stock_balances integer[] DEFAULT stock_balances_snapshot() ...

This will restore OK, but it will not execute unless the caller also sets the search_path, which is certainly not a given or even to be expected.

I have also observed the following output, which suffers the same issue:

...  role           "internal".user_role NOT NULL DEFAULT 'guest'::user_role ...


Can pg_dump have an option to output fully qualified schema?

Best
Ian Campbell

pgsql-bugs by date:

Previous
From: paziek@gmail.com
Date:
Subject: [BUGS] BUG #14822: Partition check constraint is ignored if parameter ispassed from SQL function
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] pg_dump does not fully include the schema, causing runtime errors