Re: Segmentation fault with pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Keiko Oda <keiko(at)heroku(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Segmentation fault with pg_restore
Date: 2016-09-22 19:24:51
Message-ID: 10564.1474572291@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Keiko Oda <keiko(at)heroku(dot)com> writes:
> I'm seeing "Segmentation fault" with a following pg_restore command, with
> the certain dump file (attached to this email, I had to remove some data
> from the file as the dump file contains the data that cannot be shared
> publicly, but I can reproduce this with full dump file also):

This file is corrupt. I think what's happened to it is it went through
a Unix->Windows text conversion, replacing bytes that happened to look
like newlines with \r\n.

The fact that pg_restore segfaulted isn't terribly nice, but the best
we could do is give you some nondescript message saying there's something
wrong with the file ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2016-09-22 20:54:19 Re: 9.6rc1 Background worker starting multiple times
Previous Message Tom Lane 2016-09-22 15:36:47 Re: BUG #14328: SELECT FOR UPDATE doesn't return existing row