Re: [7.0.2] problems with spinlock under FreeBSD?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [7.0.2] problems with spinlock under FreeBSD?
Date: 2000-08-24 04:05:08
Message-ID: 22194.967089908@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> looking in /var/log/messages, I'm seeing the following just before the
> crashes:

> Aug 23 12:33:47 pgsql syslogd: /dev/console: Too many open files in system: Too many open files in system
> Aug 23 12:33:47 pgsql syslogd: /var/run/utmp: Too many open files in system
> Aug 23 12:33:47 pgsql /kernel: file: table is full

That sure looks like you'd better tweak your kernel settings ... but
offhand I don't see how it could lead to "stuck spinlock" errors.
What do you get from gdb backtraces on the corefiles?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-08-24 04:54:36 Some gripes about BugTool
Previous Message Tom Lane 2000-08-24 03:56:35 Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan