From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Zsolt Ero <zsolt.ero@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16732: pg_dump creates broken backups
Date: Sun, 22 Nov 2020 11:45:34 -0300
Message-ID: <20201122144534.GA22488@alvherre.pgsql> (raw)
In-Reply-To: <CAKw-smBUUTYNJQJ21+LEOEnCqPLWfX0XVixA3eHBcAT3Nh33pQ@mail.gmail.com>
On 2020-Nov-22, Zsolt Ero wrote:
> Can you help me how can I do this?
>
> Here is what I was doing before, which triggered the bug:
>
> pg_restore --schema-only --format=custom --single-transaction $BACKUP_FILE
>
> pg_restore --list $BACKUP_FILE > dump_list.full
> grep -v "public events_map" dump_list.full > dump_list.main
>
> pg_restore --data-only --format=custom --use-list=dump_list.main --jobs=4
> $BACKUP_FILE
I'd do this:
pg_restore --list $BACKUP_FILE | grep -v "TABLE DATA public events_map" > dump_list
pg_restore -j4 --use_list=dump_list $BACKUP_FILE
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: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, zsolt.ero@gmail.com, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16732: pg_dump creates broken backups
In-Reply-To: <20201122144534.GA22488@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox