Re: invalid memory alloc request size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Janning Vygen <vygen(at)gmx(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: invalid memory alloc request size
Date: 2006-01-23 16:05:23
Message-ID: 5863.1138032323@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Janning Vygen <vygen(at)gmx(dot)de> writes:
> pg_dump: ERROR: invalid memory alloc request size 18446744073709551614
> pg_dump: SQL command to dump the contents of table "spieletipps" failed:
> PQendcopy() failed.

This looks more like a corrupt-data problem than anything else. Have
you tried the usual memory and disk testing programs?

> recent thread on HACKERS but sorry guys: i dont know how to produce a
> backtrace.

Time to learn ;-)

gdb /path/to/postgres_executable /path/to/core_file
gdb> bt
gdb> q

The core file will be somewhere under $PGDATA, named either "core" or
"core.nnnnn" depending on your kernel settings. If you don't see one
then it's probable that the postmaster was started under "ulimit -c 0".
Put "ulimit -c unlimited" in your postgres startup script, restart,
trigger the crash again.

It's also a good idea to look in the postmaster log to see if any
unusual messages appeared before the crash.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John DeSoi 2006-01-23 16:27:24 Re: What is made a mistake with SP?
Previous Message Scott Marlowe 2006-01-23 16:01:15 Re: RAID 5 and postgresql