Hitting the nfile limit
От | Michael Brusser |
---|---|
Тема | Hitting the nfile limit |
Дата | |
Msg-id | DEEIJKLFNJGBEMBLBAHCMEKHDFAA.michael@synchronicity.com обсуждение исходный текст |
Ответ на | Re: cvs version compile error (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Hitting the nfile limit
|
Список | pgsql-hackers |
We ran into problem while load-testing 7.3.2 server. From the database log: FATAL: cannot open /home/<some_path>/postgresql/PG_VERSION: File table overflow The QA engineer who ran the test claims that after server was restarted one record on the database was missing. We are not sure what exactly happened. He was running about 10 servers on HP-11, hitting them with AstraLoad. Most requests would try to update some record on the database, most run with Serializable Isolation Level. Apparently we managed to run out of the open file descriptors on the host machine. I wonder how Postgres handles this situation. (Or power outage, or any hard system fault, at this point) Is it possible that we really lost a record because of that? Should we consider changing default WAL_SYNC_METHOD? Thanks in advance, Michael.
В списке pgsql-hackers по дате отправления: