On Tue, 2004-08-10 at 19:28 -0400, Sven Willenberger wrote:
>
> Tom Lane wrote:
> > Sven Willenberger <[EMAIL PROTECTED]> writes:
> >
> >>pg_restore in malloc(): error: allocation failed
> >>Abort (core dumped)
> >
> >
> > A stack trace from that core file would be useful in figuring out what
> > the problem is... also, what PG version is this?
> >
> > regards, tom lane
>
> psql -V
> psql (PostgreSQL) 7.4.3
> contains support for command-line editing
>
<snip>
> Frame 6 - 11:
> (gdb) up 6
> #6 0x0804c9a1 in ReadStr (AH=0x805e000) at pg_backup_archiver.c:1530
> 1530 pg_backup_archiver.c: No such file or directory.
> in pg_backup_archiver.c
> (gdb) up
> #7 0x0804d2d8 in ReadToc (AH=0x805e000) at pg_backup_archiver.c:1878
> 1878 in pg_backup_archiver.c
> (gdb) up
> #8 0x0804fa94 in InitArchiveFmt_Custom (AH=0x805e000) at
> pg_backup_custom.c:196
> 196 pg_backup_custom.c: No such file or directory.
> in pg_backup_custom.c
> (gdb) up
> #9 0x0804cf7b in _allocAH (FileSpec=0xbfbfed19 "./callingdata",
> fmt=archCustom, compression=0, mode=archModeWrite)
> at pg_backup_archiver.c:1743
> 1743 pg_backup_archiver.c: No such file or directory.
> in pg_backup_archiver.c
> (gdb) up
> #10 0x0804a628 in OpenArchive (FileSpec=0x0, fmt=archUnknown) at
> pg_backup_archiver.c:103
> 103 in pg_backup_archiver.c
> (gdb) up
> #11 0x0804a22a in main (argc=5, argv=0xbfbfebe8) at pg_restore.c:333
> 333 pg_restore.c: No such file or directory.
> in pg_restore.c
>
> Let me know if you want any more details, a disassembled frame, what
> have you.
For future searches,etc, the problem was a corrupted dump file due to
ftp issues when transferring the file. Thanks, Tom, for helping diagnose
this.
Sven
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
