Postgres Pro
Downloads
Home   >   mailing lists

Too many private FDs - Mailing list pgsql-interfaces

From Rolf Lüttecke
Subject Too many private FDs
Date
Msg-id 3844DF65.FF29CA5A@gcd.de
Whole thread Raw
Responses Re: [INTERFACES] Too many private FDs  (awilliam@whitemice.org)
Re: [INTERFACES] Too many private FDs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [INTERFACES] Too many private FDs  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [INTERFACES] Too many private FDs  (awilliam@whitemice.org)
List pgsql-interfaces
Tree view 
Hi folks,

is anyone able to explain the following error-message extracted from
the "server.log"?

-- ERROR:  AllocateFile: too many private FDs demanded
-- pq_recvbuf: unexpected EOF on client connection
-- IpcMemoryCreate: shmget failed (Identifier removed) key=5432007,  size=96424, permission=600
-- SISegmentGet: failed: Identifier removed
-- FATAL 1:  CreateSharedInvalidationState: failed segment init
-- FATAL 1:  AttachSLockMemory: could not attach segment

The main postmaster-process dies, still leaving the other postgres-
processes active (but not working). This happens roundabout once a
day caused by different workstations and different functions.

A few environment information:
PostgreSQL 6.5.2 w/ SuSE 6.0 (2.0.36) running on a SNI-Primergy 070
Access-method: w/ Insight's ODBC-driver (6.5/0006) from MS-Access

Thanx in advance
- Rolf

_____________________________________________________________________ 
"Rolf Luettecke" <rluettecke@gcd.de>
Gesellschaft für
Computer- u. Datentechnik mbH 
http://www.gcd.de
Internet Business Solutions
_____________________________________________________________________

************

pgsql-interfaces by date:

Previous
From: Michael Meskes
Date:
Subject: Re: [INTERFACES] Asynchronous connection functions - patch submitted
Next
From: "PromoFutbol"
Date:
Subject: