Extracted ulimits values from postmaster pid and they look as expected: [root@00002-NfseNet ~]# ps -ef | grep /postgres postgres 2992 1 1 Nov30 ? 03:17:46 /usr/local/pgsql/bin/postgres -D /database/dbcluster root 26694 1319 0 18:19 pts/0 00:00:00 grep /postgres
[root@00002-NfseNet ~]# cat /proc/2992/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 10485760 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 1024 385725 processes Max open files 1024 4096 files Max locked memory 65536 65536 bytes Max address space 1024000000 unlimited bytes Max file locks unlimited unlimited locks Max pending signals 385725 385725 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us [root@00002-NfseNet-SGDB ~]# On Thu, Dec 11, 2014 at 6:01 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Carlos Henrique Reimer <carlos.rei...@opendb.com.br> writes: > > Yes, all lines of /etc/security/limits.conf are commented out and session > > ulimit -a indicates the defaults are being used: > > I would not trust "ulimit -a" executed in an interactive shell to be > representative of the environment in which daemons are launched ... > have you tried putting "ulimit -a >sometempfile" into the postmaster > start script? > > regards, tom lane > -- Reimer 47-3347-1724 47-9183-0547 msn: carlos.rei...@opendb.com.br
