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
Michael Brusser [EMAIL PROTECTED] writes:
Apparently we managed to run out of the open file descriptors on the host
machine.
This is pretty common if you set a large max_connections value while
not doing anything to raise the kernel nfile limit. Postgres will
follow what the kernel tells it is
I wonder how Postgres handles this situation.
(Or power outage, or any hard system fault, at this point)
Theoretically we should be able to recover from this without loss of
committed data (assuming you were running with fsync on). Is your QA
person certain that the record in question
