pg_dump and schema names

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: pg_dump and schema names
Date: 2013-08-09 04:04:55
Message-ID: 20130809040455.GA3625@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

pg_dump goes to great lengths not to hard-code the schema name into
commands like CREATE TABLE, instead setting the search_path before
creating the table; these commands:

CREATE SCHEMA xx;
CREATE TABLE xx.test(x int);

generates this output:

SET search_path = xx, pg_catalog;
CREATE TABLE test (
x integer
);

If you dump a schema and want to reload it into another schema, you
should only need to update that one search_path line. However, later in
the dump file, we hardcode the schema name for setting the object owner:

ALTER TABLE xx.test OWNER TO postgres;

Could we use search_path here to avoid the schema designation? I am not
sure this possible because while CREATE defaults to the first existing
schema in the search_path, I am not sure ALTER has the same behavior
because you are not _creating_ something with ALTER.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Sewell 2013-08-09 05:20:54 Re: pg_dump and schema names
Previous Message Jon Nelson 2013-08-09 03:58:42 Re: 9.4 regression