Re: too-may-open-files log file entries when vauuming under solaris

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Wednesday, March 5, 2014 9:17 PM
> To: Raschick, Hartmut
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] too-may-open-files log file entries when
> vauuming under solaris
>
> "Raschick, Hartmut" <Hartmut.Raschick@keymile.com> writes:
> > recently we have seen a lot of occurrences of "out of file
> descriptors:
> > Too many open files; release and retry" in our postgres log files,
...
..
.
> > in the platform specific notes (e.g. have u/limit at 256 maximum).
>
> TBH this sounds like unfounded speculation
...
..
.
>             regards, tom lane

Hmmm... FWIW, we've compiled some more info to illustrate the problem. Starting w/a sniplet from the Solaris 10 "fopen"
manpage, test programs showing the "difference" between open and fopen calls under Solaris, a postgres log file
w/extendedlogging and a diff-file of that fd.c to show how the addt'l logs were produced. I hope this makes it somewhat
clearer,i.e. no system-wide, but a per-process topic and related to that Solaris 32-bit ABI backwards compatibility...
surelynot a world-wide problem, one would agree. Nevertheless, we'd though it prudent to at least mention it. 
Btw, here's what Oracle has to say: http://www.oracle.com/technetwork/server-storage/solaris10/stdio-256-136698.html
I hope the 15K attachment gets through...

cheers,
hardy

Hartmut Raschick
Network Management Solutions
-----------------------------------
KEYMILE GmbH
Wohlenbergstr. 3
D-30175 Hannover, Germany

Phone: +49 (0)511 6747-564
Fax:   +49 (0)511 6747-777
mailto:Hartmut.Raschick@keymile.com
http://www.keymile.com

<< KEYMILE - because connectivity matters >>

Geschäftsführer/Managing Directors: Björn Claaßen, Michael Breyer, Axel Föry - Rechtsform der Gesellschaft/Legal
structure:GmbH, Sitz/Registered office: Hannover HRB 61069, Amtsgericht/Local court Hannover, USt-Id. Nr./VAT-Reg.-No.:
DE812282795, WEEE-Reg.-No.: DE 59336750