Re: invalid memory alloc request size

Janning Vygen <vygen(at)gmx(dot)de> writes:
> I shouldn't call gdb while my database is up and running, don't i?

Sure you can. Especially against a core dump --- that mode doesn't have
anything to do with the running processes.

> $ delete from spieletipps where ctid = '(3397,49)';
> Server beendete die Verbindung unerwartet

Hmm ... as far as I can think at the moment, this suggests a problem
with a toasted field; DELETE wouldn't need to look at the contents of
a target row except if it has to find and delete subsidiary toast rows.
But looking at the gdb backtrace would help to confirm or deny that.

Another thing that would be useful at this point is to get a dump of the
page containing the corrupted tuple, which we now know is block 3397 of
that table. See pg_filedump from
http://sources.redhat.com/rhdb/utilities.html
Something like "pg_filedump -i -f -R 3397 $PGDATA/base/XXXX/YYYY", where
XXXX is the database OID and YYYY is the table's relfilenode.

regards, tom lane