Re: Strange error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: a(dot)joubert(at)albourne(dot)com
Cc: Postgresql <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Strange error message
Date: 2000-10-02 06:22:49
Message-ID: 944.970467769@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-ports

Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> writes:
>>>> ERROR: UNLockBuffer: buffer 0 is not locked

> Right, I'vebuilt a new database and everything seemed fine for a while and
> now I've got this message back. It is due to the index on one of our
> tables getting messed up - at least, if we drop and recreate the index
> everything is fine. What should I do to track down what is happening?
> Compile with asserts, or run with specific logging?

Compile with asserts and -g, and get a backtrace from the ensuing
coredump. (LockBuffer *will* Assert when passed a zero. If we are
really lucky, we might see an earlier Assert failure that will give
more clue about where the zero comes from --- but if not, the backtrace
from the bogus LockBuffer call might still be useful.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-10-02 06:26:40 Re: Alpha spinlock
Previous Message Tom Lane 2000-10-02 06:16:47 pg_regress gripes

Browse pgsql-ports by date

  From Date Subject
Next Message Tom Lane 2000-10-02 06:26:40 Re: Alpha spinlock
Previous Message Adriaan Joubert 2000-10-02 05:42:33 Re: Strange error message