Re: 7.3 pg_dump with -Fc option crashes

From: Laurette Cisneros <laurette(at)nextbus(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 7.3 pg_dump with -Fc option crashes
Date: 2003-01-11 01:14:38
Message-ID: Pine.LNX.4.44.0301101712510.27364-100000@visor.corp.nextbus.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Oh goodness it's even worse as pg_restore can't read the archive from the
first pg_dump:

pg_dump -h myhost -p 5432 -f mydb.pgdmp mydb
pg_restore -l mydb.pgdmp

pg_restore: [archiver] input file does not appear to be a valid archive

Thanks,

L.
On Fri, 10 Jan 2003, Laurette Cisneros wrote:

>
> This works:
> pg_dump -h myhost -p 5432 -f mydb.cpgdmp mydb
>
> This does not:
> pg_dump -h myhost -p 5432 -Fc -f mydb.cpgdmp mydb
> Segmentation fault (core dumped)
>
> Nor does this:
> pg_dump -h myhost -p 5432 -Ft -f mydb.cpgdmp mydb
> (but I need the -Fc badly as my dbs backup up to large files)
>
> Here's a stack track (if needed):
> (adb) bt
> #0 0x080562a6 in WriteStr (AH=0x8074638,
> c=0x6c627570 <Address 0x6c627570 out of bounds>) at
> pg_backup_archiver.c:1519
> #1 0x080569b2 in WriteToc (AH=0x8074638) at pg_backup_archiver.c:1851
> #2 0x080594b2 in _CloseArchive (AH=0x8074638) at pg_backup_custom.c:802
> #3 0x080545ef in CloseArchive (AHX=0x8074638) at pg_backup_archiver.c:113
> #4 0x0804a846 in main (argc=9, argv=0xbffff4cc) at pg_dump.c:645
> #5 0x401ef306 in __libc_start_main (main=0x8049db0 <main>, argc=9,
> ubp_av=0xbffff4cc, init=0x8049634 <_init>, fini=0x8064720 <_fini>,
> rtld_fini=0x4000d2dc <_dl_fini>, stack_end=0xbffff4bc)
> at ../sysdeps/generic/libc-start.c:129
>
> Thanks,
>
>

--
Laurette Cisneros
The Database Group
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
----------------------------------
Life is an SQL old chum...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-01-11 01:18:23 Re: 7.3 pg_dump with -Fc option crashes
Previous Message Neil Conway 2003-01-11 01:08:22 help with PL/PgSQL bug