Content-Type: text/plain;
	charset=utf-8
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: <99d51fe7-c6d2-4421-9456-07ed1f5703a2@aklaver.com>
Date: Thu, 13 Feb 2025 17:17:58 +0100
Cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A9148A0-CF9C-4841-A9C0-D7E299AC4ADD@gmail.com>
References: <B0DB872D-B2A0-4323-9EA8-A7FB4567ACCB@gmail.com>
 <187f2c5d-f268-4596-bb63-c94790ae761d@aklaver.com>
 <D46171D1-80B9-4E81-BC26-D47319B90CE3@gmail.com>
 <99d51fe7-c6d2-4421-9456-07ed1f5703a2@aklaver.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Archived-At: <https://www.postgresql.org/message-id/5A9148A0-CF9C-4841-A9C0-D7E299AC4ADD%40gmail.com>
Precedence: bulk

Hi Adrian,

sorry for the late answer. I'm just too busy.

> On 7 Feb 2025, at 17:19, Adrian Klaver <adrian.klaver@aklaver.com> =
wrote:
>=20
>> With create database <options> being "template template0", this is =
what my script does. But I need the -cC options for pg_restore to get =
ACLs back. Leaving out either one of them will not get me the ACLs back.
>=20
> That does not make sense.
>=20
> Are there ACLs(privileges) in the database at all?
>=20
> What is the pg_dump command you are running?

I use this pg_dump command:

pg_dump -Fc -Z1 --quote-all-identifiers -b "${PGDATABASE}" -f =
${dumpBase}/${clusterName}.${PGDATABASE}.dump.gz >${PGDATABASE}.out =
2>${PGDATABASE}.err &

The command is embedded in a Bash script for loop that loops PGDATABASE =
over all database names inside the cluster and launches pg_dump as a =
background job. It then waits for all jobs to complete ("wait" command). =
dumpBase is just the destination directory.

If I don't use -cC, i.e. both, then the Access privileges will not be =
restored. Checking with \l just shows an empty field as usual for a =
newly created database. This happens at least with 17.2. I didn't check =
that with 17.3 yet.

I agree, from how I understood the docs I should be able to only use -C =
and not -c.

As for the data inconsistency, PostgreSQL is right. I found out that =
some clever person did a "alter table =E2=80=A6 disable trigger all" on =
a table and then manipulated data. That broke referential integrity. So, =
this case is closed.

Cheers,
Paul=