Skip site navigation (1) Skip section navigation (2)

pgsql: Don't actively violate the system limit of maximum open files

From: petere(at)postgresql(dot)org (Peter Eisentraut)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't actively violate the system limit of maximum open files
Date: 2009-03-04 09:12:49
Message-ID: 20090304091250.012EE755AA5@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Don't actively violate the system limit of maximum open files (RLIMIT_NOFILE). 
This avoids irritating kernel logs (if system overstep violations are enabled) 
and also the grsecurity alert when starting PostgreSQL.

original patch by Jacek Drobiecki

References:
http://archives.postgresql.org/pgsql-bugs/2004-05/msg00103.php
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=248967

Modified Files:
--------------
    pgsql/src/backend/storage/file:
        fd.c (r1.147 -> r1.148)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/file/fd.c?r1=1.147&r2=1.148)

pgsql-committers by date

Next:From: Peter EisentrautDate: 2009-03-04 10:55:00
Subject: pgsql: Add new SQL:2008 error codes for invalid LIMIT and OFFSET values.
Previous:From: Magnus HaganderDate: 2009-03-04 08:43:15
Subject: pgsql: Log a warning instead of shutting down the system if we can't

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group