Re: BUG #2769: "invalid memory alloc request size <n>" on startup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Chris Jones" <chris(at)cjones(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2769: "invalid memory alloc request size <n>" on startup
Date: 2006-11-21 01:43:29
Message-ID: 16495.1164073409@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Chris Jones" <chris(at)cjones(dot)org> writes:
> After several uncontrolled reboots of the server, one of my hosted sites'
> databases is giving an error on any attempt to connect to the DB. Trying to
> distill this down to the simplest case possible, I stopped the postmaster
> and ran postgres in standalone mode, with just that database. Setting the
> debug level didn't seem to accomplish anything:

> pgsql(at)maxine$ postgres -D data -d 5 drupal_dearslut
> FATAL: invalid memory alloc request size 1095237632

This looks like a problem of corrupt data in one of the system catalogs
or its indexes, but there's not enough info here to guess where.

> I used to be decent with gdb, so let me know if there's anything I can do as
> far as backtraces, etc.

Try setting a breakpoint at errfinish() and backtracing from there.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2006-11-21 01:54:16 Re: BUG #2767: Bug in avg(interval)
Previous Message Tom Lane 2006-11-21 01:33:42 Re: BUG #2766: erratic segfault in libpq/DBD::Pg