Re: BUG #2769: "invalid memory alloc request size " on startup - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2769: "invalid memory alloc request size " on startup
Date
Msg-id 16495.1164073409@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2769: "invalid memory alloc request size " on startup  ("Chris Jones" <chris@cjones.org>)
Responses Re: BUG #2769: "invalid memory alloc request size " on
List pgsql-bugs
"Chris Jones" <chris@cjones.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@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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2768: dates before year 1600 in timestamptz column give strange results
Next
From: Tom Lane
Date:
Subject: Re: BUG #2766: erratic segfault in libpq/DBD::Pg