Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject

Поиск
Список
Период
Сортировка
Искать
От
Heikki Linnakangas
Тема
Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject
Дата
Msg-id
462CA31F.4040403@enterprisedb.com
Ответ на
Список
Дерево обсуждения
Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct "Dorochevsky,Michel" <michel.dorochevsky@softcon.de>
Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject Heikki Linnakangas <heikki@enterprisedb.com>
Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject Dave Page <dpage@postgresql.org>
Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct Tom Lane <tgl@sss.pgh.pa.us>
Dorochevsky,Michel wrote:
>> Michel; I've uploaded an 8.2.3 postgres.exe to 
>> http://developer.pgadmin.org/~dpage/postgres-8.2.3-debug.zip. This is 
>> the same as the release version, but configured with --enable-debug 
>> --enable-cassert, and patched with Tom's patch.
>>
>> Regards, Dave.
> 
> Dave,
> Thanks a lot. You can download the results at
>     www.dorochevsky.de/infos/postgresql-2007-04-23_130939.zip
> run with the debug version of postgres you provided.
> 
> Hope this helps to clarify what is going on.

Thanks!

It looks like it's a relation-lock that's being lost. That's all I can 
say :(.

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...)

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com
В списке pgsql-bugs по дате отправления
От: Dorochevsky,Michel
Дата:
От: Dave Page
Дата:
FAQ