Michael <[EMAIL PROTECTED]> writes:
> Here is backtrace from gdb postgres postgres.core:
> (gdb) bt
> #0 0x485dc277 in kill () from /lib/libc.so.7
> #1 0x485dc1d6 in raise () from /lib/libc.so.7
> #2 0x485dadda in abort () from /lib/libc.so.7
> #3 0x0824c075 in errfinish ()
> #4 0x0824c8b1 in elog_finish ()
> #5 0x081c9184 in s_lock ()
> #6 0x081c8d48 in LWLockAcquire ()
> #7 0x081c61ec in LockAcquire ()
Apparently s_lock_stuck ... though you might want to look at
postmaster's stderr output to confirm that.
> I run FreeBSD 7.0-BETA1 on Dual-Core AMD Opteron(tm) Processor 2216
> (2394.01-MHz 686-class CPU) with ULE scheduler
> PostgreSQL 8.2.5
> I can't find what triggers this behavior (it started core dumping
> after upgrading from FreeBSD 6.2)
Did you recompile Postgres? Maybe you need to. I dunno what the
differences are between 6.2 and 7 ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
