Tom Lane wrote:
Olivier Hubaut <[EMAIL PROTECTED]> writes:
PANIC: could not open transaction-commit log directory
(/usr/local/pgsql/annot/pg_clog): Too many open files
But it's amazing to me that i had to reduce it so much as the postmaster
is almost the only application running on this serv
Olivier Hubaut <[EMAIL PROTECTED]> writes:
>>> PANIC: could not open transaction-commit log directory
>>> (/usr/local/pgsql/annot/pg_clog): Too many open files
> But it's amazing to me that i had to reduce it so much as the postmaster
> is almost the only application running on this server.
Oh
Olivier Hubaut <[EMAIL PROTECTED]> writes:
> But it's amazing to me that i had to reduce it so much as the postmaster
> is almost the only application running on this server. There only 3 or 4
> simultaneous connections and the kernel max files is set to 12500!
But how many open files are needed
Tom Lane wrote:
Olivier Hubaut <[EMAIL PROTECTED]> writes:
PANIC: could not open transaction-commit log directory
(/usr/local/pgsql/annot/pg_clog): Too many open files
Try reducing max_files_per_process (in postgresql.conf) and/or
increasing the kernel's limit on number of open files (I think
Olivier Hubaut <[EMAIL PROTECTED]> writes:
> PANIC: could not open transaction-commit log directory
> (/usr/local/pgsql/annot/pg_clog): Too many open files
Try reducing max_files_per_process (in postgresql.conf) and/or
increasing the kernel's limit on number of open files (I think
you set this v
Hi,
On PostgreSQL 7.3.3 on MacOS X 10.2, the ANALYZE command sometimes crash
and I don't know why! I've tried it some binaries copies of the DB, it's
a totally random behaviour.
When it crahes, I get this message:
PANIC: could not open transaction-commit log directory
(/usr/local/pgsql/annot
