Re: Segmentation fault during restoration of compressed(.gz) database

sulmansarwar wrote:
> Hi,
>
> I am new to PostgreSQL. I have been trying to restore a compressed(.gz)
> database using
>
> gunzip -c filename.gz | psql dbname
>
> After some 8 or 9 tables are restored the program exists giving error:
> Segmentation Fault.

> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0x00000000014fffff
> Crashed Thread: 0
>
> Thread 0 Crashed:
> 0 psql 0x0000d3b5 gets_fromFile + 296
> 1 psql 0x0000df73 MainLoop + 613
> 2 psql 0x00010d7a main + 2394
> 3 psql 0x00003fc2 _start + 216
> 4 psql 0x00003ee9 start + 41
>
> Thread 0 crashed with X86 Thread State (32-bit):
> eax: 0x014fffff ebx: 0x0000d29c ecx: 0x00000000 edx: 0x01500000
> edi: 0x00302866 esi: 0xbffff674 ebp: 0xbffff3b8 esp: 0xbfffef80
> ss: 0x0000001f efl: 0x00010216 eip: 0x0000d3b5 cs: 0x00000017
> ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
> cr2: 0x014fffff

If I'm reading that stack-trace correctly, it's crashed while reading
commands from STDIN (MainLoop > gets_fromFile). It's unlikely that
something so basic has a bug, which suggests something else is
scribbling over a pointer that gets_fromFile is using.

People smarter than me will have to provide more help, but I can tell
you some of the details they'll want.

1. Exact version of PostgreSQL and how you installed it (package,
compiled from source etc). Try the output of pg_config too.

2. Anything unusual about the table it fails to restore (unusual data
types, very large data values, that sort of thing).

3. Is it reproducible from a decompressed version of "filename"?

4. Can you reduce it to a short example that can be tested on other
machines?

--
Richard Huxton
Archonet Ltd