> Von: Tom Lane [mailto:...]
> Gesendet: Freitag, 20. April 2007 18:14
> An: Dorochevsky,Michel
> Cc: pgsql-bugs@postgresql.org
> Betreff: Re: AW: [BUGS] BUG #3245: PANIC: failed to re-find shared lock
object
>
> "Dorochevsky,Michel"
writes:
> > Two
> Question: do you have any leftover files in $PGDATA/pg_twophase ?
>
> I'm wondering why the log contains no warning messages about stale
> two-phase state files. It looks to me like the system should have
> found the two-phase file still there upon restart, but the transaction
> should have been
> 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 downloa
> Von: Tom Lane [mailto:[EMAIL PROTECTED]
> So, which of your tables has OID 417227? Easiest way to check is
> select 417227::regclass
>
Tom,
Currently a table with name
requireditemtypes_mill7b7c7621
has the object id 417227.
I did restart the DB server in the meantime several times.
I
> From: Dave Page [mailto:[EMAIL PROTECTED]
> 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 mu
-Ursprüngliche Nachricht-
> Von: Tom Lane [mailto:[EMAIL PROTECTED]
> > "Dorochevsky,Michel" <[EMAIL PROTECTED]> writes:
> > Here are two panic runs with the Heikki's LOCK_DEBUG patched postgres:
> >www.dorochevsky.de/infos/PostgresPanicProble
> Tom Lane wrote
> I've committed a fix for this; it'll be in the next set of releases.
>
> regards, tom lane
Tom,
Thanks a lot for all your work and help, I am very impressed by the
PostgreSQL Team.
Just a last question.
Are you planning to provide a binary fix for 8.2.x?
