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

From: "Dorochevsky,Michel" <michel(dot)dorochevsky(at)softcon(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, "Dorochevsky,Michel" <michel(dot)dorochevsky(at)softcon(dot)de>
Subject: Re: BUG #3245: PANIC: failed to re-find shared loc k ob ject
Date: 2007-04-21 19:38:35
Message-ID: C12B71B21705A04C9B9C3E9300430CAFA9701E@jupiter.softcon-its.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 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 marked already committed.
>
> BTW, can you tell whether the failing transactions actually were committed
> --- are their effects still visible in the database?
>
> regards, tom lane
Tom,
Thanks for your continuous support, I appreciate a lot.

The failing transaction is visible in the database after restart, I have
checked three of the last inserts, e.g.
2007-04-21 18:06:18.921 20160 LOG: execute <unnamed>: insert into
CHECKRESULT (COMMENT, POSITIONINCHAIN, MDSD_OPT_LOCK, MDSD_CLASS, ID) values
($1, $2, $3, 'CheckResult', $4)
2007-04-21 18:06:18.921 20160 DETAIL: parameters: $1 = 'geht schon', $2 =
'2', $3 = '2007-04-21 18:06:18.64', $4 = '4046'
is visible. I can tell from the application, that this record will never be
updated later on and always has the current timestamp.

I have no leftover file in $PGDATA/pg_twophase, it is empty.

Best Regards
-- Michel

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marcin Waldowski 2007-04-21 21:07:08 Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Previous Message Tom Lane 2007-04-21 18:30:32 Re: BUG #3245: PANIC: failed to re-find shared lock ob ject