public inbox for [email protected]  

help / color / mirror / Atom feed

From: Greg Sabino Mullane <[email protected]>
To: Daniel Verite <[email protected]>
Cc: Paul Foerster <[email protected]>
Cc: Adrian Klaver <[email protected]>
Cc: Pgsql-General List <[email protected]>
Subject: Re: libc to libicu via pg_dump/pg_restore?
Date: Fri, 7 Feb 2025 09:53:10 -0500
Message-ID: <CAKAnmmJT_3p+Dtbi7z63u1aYXjmR_D5FK9DKfxWf9hWwC60ovg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

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

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: libc to libicu via pg_dump/pg_restore?
  In-Reply-To: <CAKAnmmJT_3p+Dtbi7z63u1aYXjmR_D5FK9DKfxWf9hWwC60ovg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox