Prem Gopalan wrote:
> We run a multithreaded application that uses postgres 7.4 on Linux
> 2.4.18, dual cpu Xeon processor machine. We have occassional weird
> crashes and have tried a lot of things to reproduce them in house, but
> in vain. We do have coredumps and I have listed the backtraces and
> their common characteristics here.
Whether your client is multi-threaded or not should have no affect on
the postmaster and any crashes you see there.
This part of the backtrace seems significant:
> #3 0x081a767e in elog_finish (elevel=20, fmt=0x8235680 "invalid
> memory alloc request size %lu")
I wonder if you are allocating too much memory. Looking at the 7.4 code
I see these all as ERROR, not FATAL (backend exits) or PANIC (postmaster
exits), so it shouldn't be crashing anything:
./backend/utils/mmgr/mcxt.c: elog(ERROR, "invalid memory
alloc request size %lu",
./backend/utils/mmgr/mcxt.c: elog(ERROR, "invalid memory
alloc request size %lu",
./backend/utils/mmgr/mcxt.c: elog(ERROR, "invalid memory
alloc request size %lu",
./backend/utils/mmgr/mcxt.c: elog(ERROR, "invalid memory
alloc request size %lu",
Would you send over a backtrace that shows more levels above this?
Can you reproduce this crash on demand?
I can't imagine why you would get this error. I wonder if you have a
problem with bad memory on that machine?
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
