From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sylvain Cuaz <sylvain@ilm-informatique.fr>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Restoring only a subset of schemas
In-reply-to: <7d869dac-5fe0-488c-a7a1-436b1d939057@ilm-informatique.fr>
References: <7d869dac-5fe0-488c-a7a1-436b1d939057@ilm-informatique.fr>
Comments: In-reply-to Sylvain Cuaz <sylvain@ilm-informatique.fr>
	message dated "Mon, 17 Mar 2025 15:57:04 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <4009719.1742225376.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 17 Mar 2025 11:29:36 -0400
Message-ID: <4009720.1742225376@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/4009720.1742225376%40sss.pgh.pa.us>
Precedence: bulk

Sylvain Cuaz <sylvain@ilm-informatique.fr> writes:
>  =C2=A0=C2=A0=C2=A0 Now if I want to restore from a full dump of this DB=
, but with only one "cXXX" and the "Common" =

> schema :
> - if I pass --create --schema=3DCommon, then the CREATE SCHEMA is missin=
g, i.e. it only emits data =

> inside "Common" and the restore fails.
> - if I could pass --create --exclude-schema=3D'c*' (fictional notation a=
s patterns are only recognized =

> by pg_dump), then all schemas would be created, with no data inside exce=
pt for "Common". Creating =

> all schemas is a waste of time, but more importantly would make restorin=
g other schemas more =

> difficult (e.g. rows should be inserted before creating foreign keys).

In general, the solution for edge-case restore selection needs is to
make a list of the dump's contents with "pg_restore -l", edit out what
you don't want using any method you like, then use the edited list with
"pg_restore -L".

While I'd be in favor of improving pg_restore to accept wild-card
patterns, I'm very hesitant to start inventing new kinds of selection
switches for it.  The interactions between such switches would be a
mess.

			regards, tom lane