Re: stuck spinlock. Aborting. What does this mean?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Bertheau <twanger(at)bluetwanger(dot)de>
Cc: PostgreSQL-Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: stuck spinlock. Aborting. What does this mean?
Date: 2001-12-18 14:58:53
Message-ID: 13162.1008687533@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Markus Bertheau <twanger(at)bluetwanger(dot)de> writes:
> On Fri, 2001-12-14 at 23:31, Tom Lane wrote:
>> It looks to me like your postmaster crashed because there were no free
>> file descriptors left in the system:

> Does 7.1 or 7.2 behave differently when confronted with such a
> situation?

I believe we've fixed the particular case you exhibited as of 7.1.
Can't swear that there are no similar problems anywhere, however.

In practice, being out of file descriptors will take down most parts
of a Unix system, so whether the postmaster is bulletproof or not is
not all that interesting a question. The only practical way to proceed
is to make sure that the situation never happens. 7.2 has a config
variable that can be used to limit Postgres' appetite for file
descriptors, even when the kernel lies about its ability to provide
lots of descriptors (unfortunately a common practice).

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-12-18 16:24:56 Re: Bug #542: 7.1.3 will not compile/install on SCO Open Server 5.0.4/5.0.5
Previous Message Tony Nicol 2001-12-18 11:20:28 Problem creating database using windows2k + cygwin + cygipc