| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Pgsql-General List <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: libc to libicu via pg_dump/pg_restore? |
| Date: | 2025-02-07 14:53:10 |
| Message-ID: | CAKAnmmJT_3p+Dtbi7z63u1aYXjmR_D5FK9DKfxWf9hWwC60ovg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-02-07 16:13:15 | Re: libc to libicu via pg_dump/pg_restore? |
| Previous Message | Daniel Verite | 2025-02-07 13:29:05 | Re: libc to libicu via pg_dump/pg_restore? |