From: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: libc to libicu via pg_dump/pg_restore? |
Date: | 2025-02-06 17:37:25 |
Message-ID: | 12488E77-4D0F-46B1-B7C9-BFA1D61D6B62@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Guillaume,
> On 6 Feb 2025, at 15:51, Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com> wrote:
>
> You're right. Now I see the "create database" query in your previous email. I should have been more careful, sorry for the noise.
No problem.
> Well, the doc says that --disable-triggers is only relevant for data-only restore, which is not your use case. So you don't need it and it won't help you.
Yes, I found that out too. But it doesn't hurt. 🤣
> Me neither. But another comment. You create the database, so there should be no objects in it. Why do you use the -c, -C, and --if-exists options? Try without them. On a new database, you should only need:
>
> pg_restore -d mydb mydb.dump.gz
I need -C because I need ACLs to be recreated too. I tried with -C only, i.e. no -c but that doesn't work for some reason. The --if-exists is a script remnant of my past tries to suppress some messages. I'll try removing that as I rewrote my create database script which runs before importing.
Cheers,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Leach | 2025-02-06 17:58:08 | Re: How to perform a long running dry run transaction without blocking |
Previous Message | Adrian Klaver | 2025-02-06 17:15:55 | Re: How to perform a long running dry run transaction without blocking |