Re: problem with locks on head, backend crash

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: problem with locks on head, backend crash
Date: 2008-04-07 14:55:35
Message-ID: 162867790804070755w102078a7mce37f8b6a9b42754@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/04/2008, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Pavel Stehule escribió:
>
>
> > WARNING: problem in alloc set MessageContext: req size > alloc size
> > for chunk 0x8b6d1e0 in block 0x8b6bb50
> > WARNING: problem in alloc set MessageContext: req size > alloc size
> > for chunk 0x8b6d1e0 in block 0x8b6bb50
>
>
> I suggest you make distclean and rebuild the whole thing from scratch --
> I have seen these kind of problems when a loadable module is not built
> the same as the backend, for example.
>

I did it, but maybe there was some ??? I can't to repeat it after restart

Pavel

> --
> Alvaro Herrera http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-04-07 15:34:33 Feature freeze status
Previous Message Alvaro Herrera 2008-04-07 14:51:46 Re: problem with locks on head, backend crash