Re: libc to libicu via pg_dump/pg_restore?
От | Adrian Klaver |
---|---|
Тема | Re: libc to libicu via pg_dump/pg_restore? |
Дата | |
Msg-id | e89a7bb3-242d-4410-bd44-9cef059a5b3b@aklaver.com обсуждение исходный текст |
Ответ на | Re: libc to libicu via pg_dump/pg_restore? (Paul Foerster <paul.foerster@gmail.com>) |
Ответы |
Re: libc to libicu via pg_dump/pg_restore?
|
Список | pgsql-general |
On 2/6/25 09:37, Paul Foerster wrote: > Hi Guillaume, > >> On 6 Feb 2025, at 15:51, Guillaume Lelarge <guillaume.lelarge@dalibo.com> wrote: >> >> You're right. Now I see the "create database" query in your previous email. I should have been more careful, sorry forthe noise. > > No problem. > >> Well, the doc says that --disable-triggers is only relevant for data-only restore, which is not your use case. So youdon'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 rewrotemy create database script which runs before importing. By ACL do you mean roles? If so roles are global to the cluster not the database, so I am not seeing -C being relevant. If not you will need to be more specific about what you are referring to. > > Cheers, > Paul > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: