Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Subject: Re: libc to libicu via pg_dump/pg_restore?
From: Paul Foerster <paul.foerster@gmail.com>
In-Reply-To: <2256966c-446f-4607-a47d-04b895b0747b@dalibo.com>
Date: Thu, 6 Feb 2025 12:20:08 +0100
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A2A897E-AD8B-47F7-A29F-980D57425AD9@gmail.com>
References: <B0DB872D-B2A0-4323-9EA8-A7FB4567ACCB@gmail.com>
 <2256966c-446f-4607-a47d-04b895b0747b@dalibo.com>
To: Guillaume Lelarge <guillaume.lelarge@dalibo.com>
Archived-At: <https://www.postgresql.org/message-id/7A2A897E-AD8B-47F7-A29F-980D57425AD9%40gmail.com>
Precedence: bulk

Hi Guillaume,

> On 6 Feb 2025, at 11:13, Guillaume Lelarge =
<guillaume.lelarge@dalibo.com> wrote:
>=20
> You probably don't need --disable-triggers. You should fix errors in =
the order they appear. The first one is on the drop of the database:
>=20
> ERROR:  cannot drop the currently open database
>=20
> pg_restore can't drop the database because it's connected to the =
database. When you use -c and -C options, you can't connect to the =
database you want to restore to. You have to connect to another =
database, such as postgres, so that it can do the drop and the create. =
After both are done, it will connect to the just-created database to do =
the restore step.
>=20
> Look at the pg_restore man page =
(https://www.postgresql.org/docs/current/app-pgrestore.html). It says on =
the --create option:
>=20
> When this option is used, the database named with -d is used only to =
issue the initial DROP DATABASE and CREATE DATABASE commands. All data =
is restored into the database name that appears in the archive.

This is intended because the dump contains a create database statement =
which creates the database with libc which is exactly what I do NOT =
want. I want it to be a libicu database. So I pre-create it as such and =
inhibit recreation by pg_restore by sitting on it with a session. So the =
first message about the database not being created is expected and can =
be ignored. This works fine for all databases so far.

My problem is the constraint violation which inhibits the foreign key =
contraints from being created.

Everything works for all databases. Only this one has that problem. And =
since I disabled triggers during restore, that shouldn't be a problem =
either.

Btw., the parent table contains the rows in question. So they are =
imported. I just can't make out why there is a problem.

Cheers,
Paul=