From: | Florian Baumert <fb(at)plt(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #456: postgres dumps core in initlocalbuffer |
Date: | 2001-09-20 09:37:44 |
Message-ID: | 3BA9B8E8.9950A92D@plt.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
thank you for your fast answer. I will try to upgrade, with over 20
production databases not a one-hour job :-)
I will report results to you...
Am I the only one, where this occured??
Greetings
Florian
Tom Lane wrote:
>
> pgsql-bugs(at)postgresql(dot)org writes:
> > Stacktrace is:
>
> > #0 0x812ac0c in chunk_free (ar_ptr=0x81cb860, p=0xd4ef05d3) at malloc.c:3125
> > #1 0x812a4d3 in chunk_alloc (ar_ptr=0x81cb860, nb=7176) at malloc.c:2612
> > #2 0x8129f8f in __libc_malloc (bytes=7168) at malloc.c:2714
>
> This looks like malloc's bookkeeping data structures must have gotten
> clobbered, perhaps by a wild store operation or freeing a chunk twice
> or some such. The error is doubtless somewhere in the postmaster,
> not in InitLocalBuffer. Before you expend effort trying to hunt it
> down, I'd suggest updating to the latest stable release, 7.1.3 ---
> the problem may be fixed already. If that doesn't help, consider
> linking the postmaster with a debugging malloc package, such as Electric
> Fence...
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2001-09-20 13:15:18 | Bug #458: serial data type problem |
Previous Message | pgsql-bugs | 2001-09-19 18:47:48 | Bug #457: foreign keys are broken |