Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> writes:
> we've suddenly started getting this error message out of postgres
> (7.0.2). Does anybody know where it comes from?
> ERROR: UNLockBuffer: buffer 0 is not locked
Evidently something is passing an invalid buffer number to LockBuffer
in src/backend/storage/buffer/bufmgr.c. (0 is InvalidBuffer, but
LockBuffer won't notice that unless you compiled with asserts enabled.)
Whatever the bug is, it's not directly LockBuffer's fault.
What exactly are you doing that provokes this message?
regards, tom lane
In response to
pgsql-ports by date
|Next:||From: Bruce Momjian||Date: 2000-09-30 02:42:12|
|Subject: Re: [PORTS] Locale bug|
|Previous:||From: Adriaan Joubert||Date: 2000-09-29 14:46:44|
|Subject: Strange error message|
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2000-09-29 16:24:16|
|Subject: Re: Installation layout is still hazardous for shared
|Previous:||From: Lamar Owen||Date: 2000-09-29 14:47:33|
|Subject: Re: Installation layout is still hazardous for shared prefixes|