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

Started by Dorochevsky,Michelalmost 19 years ago5 messagesbugs
Jump to latest
#1Dorochevsky,Michel
michel.dorochevsky@softcon.de

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.

Best Regards
-- Michel

#2Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Dorochevsky,Michel (#1)
Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject

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

#3Dave Page
dpage@pgadmin.org
In reply to: Heikki Linnakangas (#2)
Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject

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.

Regards, Dave

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Dorochevsky,Michel (#1)
Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct

"Dorochevsky,Michel" <michel.dorochevsky@softcon.de> writes:

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.

So, which of your tables has OID 417227? Easiest way to check is
select 417227::regclass

regards, tom lane

#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Dorochevsky,Michel (#1)
Re: BUG #3245: PANIC: failed to re-find shared loc k ob je ct

Michel, could you show us all the non-default entries in your
postgresql.conf? Just wondering if there might be something relevant...

regards, tom lane