Re: Database restore fails - before posting to pgsql-hackers

[Paul Bente <..hidden..>]

Before posting to pgsql-hackers I thought it would be clearer to  
state the specific pg_dump command used by ledgersmb to create the  
backup file. Please edit the following to the correct translation of  
the Perl code. It was not clear to me how or where the file spec was  
included, but I know nothing about Perl.:

pg_dump -U ledgersmb -h localhost -Fc -p 5432 compbdata ??-f /path/to/ 
compbdata-1.2.0-20071120.sqlc??  or? ?? > path/to/ 
compbdata-1.2.0-20071120.sqlc ??

Many thanks for your help.

On Nov 28, 2007, at 12:37 PM, Joshua D. Drake wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 28 Nov 2007 12:32:24 -0500
> Paul Bente <..hidden..> wrote:
>
> > Ledgersmb-1.2.9 + latest AA.pm, CT.pm, OE.pm, and Sysconfig.pm;
> > PostgreSQL 8.2.4; Mac OSX 10.4.10
> > Use System > Backup > Save to File to create a backup file. Attempt
> > to restore the database failed as follows:
> >
> > postgres$ pg_restore -d compbdata /Users/pfb/Accounting/LedgerSMB/
> > Backups/compbdata-1.2.0-20071120.sqlc
> > pg_restore(24895) malloc: *** vm_allocate(size=3154120704) failed
> > (error code=3)
> > pg_restore(24895) malloc: *** error: can't allocate region
> > pg_restore(24895) malloc: *** set a breakpoint in szone_error to  
> > debug
> > pg_restore: [archiver] out of memory
> >
> > Setting the pg_restore -a flag to just restore the data and not the
> > schema gives the same result.
>
> This is clearly a PostgreSQL issue and possibly a bug based on the
> malloc error (although the bug might be in glibc). Please post this to
> pgsql-hackers with the same description.