Well, thanks to everybody who helped!
It was indeed the problem with opening files - the limit was set
to 1024 with more than 100 possible backends...
Well, I suppose it wouldn't hurt to change the error message in
the future versions of Postgres, 'cause now it is somewhat...
misleading... ;->
Greetings, The Hermit Hacker!
At 21.09.2000, 13:34, you wrote:
>> Well, last question then: I wasn't too specific, but the problem
>> with this crash is that not ONE SINGLE backend fails, but ALL OF
>> THEM AT ONCE: someone comes running to me and shouts 'our site is
>> down!', when I login and type 'ps eax | grep postgres' there
>> are no postgres processes in memory... Which is strange, as I
>> connect to Postgres from PHP, and use `persistent` connections, so
>> the backends which are in memory should have already read their
>> PG_VERSIONs...
>> Is it as it should be with ENFILE failure?
THH> that is as it was when we were hitting it ... we are actually running a db
THH> on 4 seperate ports, and we would see one db beign down and the rest
THH> running happily along ... as soon as one db goes for that last slot and
THH> can't find it, that one would completely shut down, as its the 'parent
THH> process' that appears to be the one going for it ...
--
Yours, Alexey V. Borzov
