Re: Segfault when restoring -Fd dump on current HEAD

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: depesz(at)depesz(dot)com, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Segfault when restoring -Fd dump on current HEAD
Date: 2019-02-25 15:15:31
Message-ID: 20190225151531.GP28750@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 25, 2019 at 11:01:05AM +0100, Dmitry Dolgov wrote:
> > On Mon, Feb 25, 2019 at 8:45 AM hubert depesz lubaczewski <depesz(at)depesz(dot)com> wrote:
> >
> > I did upgrade of my test pg. Part of this is pg_dump -Fd of each
> > database, then upgrade binaries, then initdb, and pg_restore.
> >
> > But - I can't restore any database that has any data - I get segfaults.
>
> Thank for reporting. Unfortunately, I can't reproduce this issue on the master
> (for me it's currently bc09d5e4cc) with the dump you've provided - do I need to
> do something more than just pg_restore to trigger it?

What's crashing for me is restoring the (12dev) dumpfile using v11 psql:

[pryzbyj(at)database tmp]$ pg_restore backup-20190225074600.10361-db-depesz.dump >/dev/null
Segmentation fault (core dumped)
[pryzbyj(at)database tmp]$ pg_restore -V
pg_restore (PostgreSQL) 11.2

I would restore dump into v12dev and re-dump and compare dump output, except it
seems like pg_restore -d no longer restores into a database ??

[pryzbyj(at)database tmp]$ PGHOST=/tmp PGPORT=5678 PATH=~/src/postgresql.bin/bin pg_restore backup-20190225074600.10361-db-depesz.dump -d postgres |wc -l
44

Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2019-02-25 15:30:00 Re: Remove Deprecated Exclusive Backup Mode
Previous Message Dean Rasheed 2019-02-25 14:36:30 Re: INSERT ... OVERRIDING USER VALUE vs GENERATED ALWAYS identity columns