Skip site navigation (1) Skip section navigation (2)

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

From: "Chris Jones" <chris(at)cjones(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2769: "invalid memory alloc request size <n>" on startup
Date: 2006-11-19 07:33:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2769
Logged by:          Chris Jones
Email address:      chris(at)cjones(dot)org
PostgreSQL version: 8.0.9
Operating system:   NetBSD 2.0.2
Description:        "invalid memory alloc request size <n>" on startup

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

The logs have only that 1 line in them, as well.

 PostgreSQL 8.0.9 on i386--netbsdelf, compiled by GCC gcc (GCC) 3.3.3
(NetBSD nb3 20040520)

maxine$ uname -a
NetBSD 2.0.2 NetBSD 2.0.2 (GENERIC) #0: Wed Mar 23
08:53:42 UTC 2005 

I used to be decent with gdb, so let me know if there's anything I can do as
far as backtraces, etc. Alternatively, if it's possible to get a consistent
dump of this DB, I could just upgrade to 8.1.



pgsql-bugs by date

Next:From: BrahmaDate: 2006-11-19 12:59:05
Subject: BUG #2770: tomcat connection pool
Previous:From: Mikko TiihonenDate: 2006-11-19 02:00:58
Subject: BUG #2768: dates before year 1600 in timestamptz column give strange results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group