BUG #2769: "invalid memory alloc request size " on startup
От | Chris Jones |
---|---|
Тема | BUG #2769: "invalid memory alloc request size |
Дата | |
Msg-id | 200611190733.kAJ7XxXu008019@wwwmaster.postgresql.org обсуждение исходный текст |
Ответы |
Re: BUG #2769: "invalid memory alloc request size |
Список | pgsql-bugs |
The following bug has been logged online: Bug reference: 2769 Logged by: Chris Jones Email address: chris@cjones.org PostgreSQL version: 8.0.9 Operating system: NetBSD 2.0.2 Description: "invalid memory alloc request size <n>" on startup Details: 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 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 maxine.cjones.org 2.0.2 NetBSD 2.0.2 (GENERIC) #0: Wed Mar 23 08:53:42 UTC 2005 jmc@faith.netbsd.org:/home/builds/ab/netbsd-2-0-2-RELEASE/i386/200503220140Z -obj/home/builds/ab/netbsd-2-0-2-RELEASE/src/sys/arch/i386/compile/GENERIC i386 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. Chris
В списке pgsql-bugs по дате отправления: