Re: stuck spinlock. Aborting. What does this mean? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: stuck spinlock. Aborting. What does this mean?
Date
Msg-id 13162.1008687533@sss.pgh.pa.us
Whole thread Raw
In response to Re: stuck spinlock. Aborting. What does this mean?  (Markus Bertheau <twanger@bluetwanger.de>)
List pgsql-bugs
Markus Bertheau <twanger@bluetwanger.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

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #541: [JDBC] DatabaseMetaData.getTables() does not return tables with rules on them
Next
From: Tom Lane
Date:
Subject: Re: Bug #542: 7.1.3 will not compile/install on SCO Open Server 5.0.4/5.0.5