MIME-Version: 1.0
References: <D46171D1-80B9-4E81-BC26-D47319B90CE3@gmail.com> <669e44d4-01fd-4ae2-9918-4396a7f8f070@manitou-mail.org>
In-Reply-To: <669e44d4-01fd-4ae2-9918-4396a7f8f070@manitou-mail.org>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 7 Feb 2025 09:53:10 -0500
Message-ID: <CAKAnmmJT_3p+Dtbi7z63u1aYXjmR_D5FK9DKfxWf9hWwC60ovg@mail.gmail.com>
Subject: Re: libc to libicu via pg_dump/pg_restore?
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Paul Foerster <paul.foerster@gmail.com>, Adrian Klaver <adrian.klaver@aklaver.com>, 
	Pgsql-General List <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000935829062d8e8619"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmJT_3p%2BDtbi7z63u1aYXjmR_D5FK9DKfxWf9hWwC60ovg%40mail.gmail.com>
Precedence: bulk

--000000000000935829062d8e8619
Content-Type: text/plain; charset="UTF-8"

I'm not sure why we are focused on the other errors - the database fails to
get dropped (or created), so future errors are to be expected.

pg_restore should be run with the --exit-on-error flag, and handle the
errors one by one as someone mentioned upthread.

I would use the --section=pre-data --section=data and --section=post-data
flags to pg_dump to create (for the pre-data) a small and editable file so
you can tweak the CREATE DATABASE as you please.

pg_dump mydb --clean --create --section=pre-data --file=mydb.pre.pg

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

--000000000000935829062d8e8619
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m not sure why we are focused on the other errors - =
the database fails to get dropped (or created), so future errors are to be =
expected.=C2=A0<div><br></div><div>pg_restore should be run with the --exit=
-on-error flag, and handle the errors one by one as someone mentioned upthr=
ead.<div><br></div><div>I would use the --section=3Dpre-data --section=3Dda=
ta and --section=3Dpost-data flags to pg_dump to create (for the pre-data) =
a small and editable file so you can tweak the CREATE DATABASE as you pleas=
e.</div><div><br></div><div>pg_dump mydb --clean --create --section=3Dpre-d=
ata --file=3D<a href=3D"http://mydb.pre.pg">mydb.pre.pg</a></div><div><br><=
/div><div>Cheers,</div><div>Greg</div><div><br></div><div>--<br>Crunchy Dat=
a - <a href=3D"https://www.crunchydata.com">https://www.crunchydata.com</a>=
<br>Enterprise Postgres Software Products &amp; Tech Support</div><div><br>=
</div></div></div>

--000000000000935829062d8e8619--