Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject - Mailing list pgsql-bugs

From Dorochevsky,Michel
Subject Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject
Date
Msg-id C12B71B21705A04C9B9C3E9300430CAFA970FF@jupiter.softcon-its.de
Whole thread Raw
Responses Re: BUG #3245: PANIC: failed to re-find shared loc k o b ject
List pgsql-bugs
> From: Dave Page [mailto:dpage@postgresql.org]
> Heikki Linnakangas wrote:
> > Dave, could you do another build with LOCK_DEBUG enabled? Michel, could
> > you please add trace_locks=on to postgresql.conf, and run the test one
> > more time with the LOCK_DEBUG-enabled build. That should give us a much
> > better picture of what's happening. (be warned, it can generate a lot of

> > log...)
> >
> Sure - Michel, please download from
> http://developer.pgadmin.org/~dpage/postgres-8.2.3-debug2.zip.
>
> This is the same as the release version, but with
>
> --enable-debug
> --enable-cassert
> -DLOCK_DEBUG
> Tom's patch
> Heikki's LOCK_DEBUG patch.
>
Tom and Heikki,

Here are two panic runs with the Heikki's LOCK_DEBUG patched postgres:
   www.dorochevsky.de/infos/PostgresPanicProblem-2007-04-23.zip

The second one is shorter. I have also provided the postgres.conf for Tom.

Best Regards
-- Michel

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct
Next
From: Magnus Hagander
Date:
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298