Mathieu Bruneau wrote:
I never tried the falcon engine, but could it be that mysql is running
out of file descriptor ?
That's less likely with Falcon than with engines that put each
table and index in its own file. By default, Falcon tables share
a single tablespace.
Regards,
Ann
--
Mariella Petrini wrote:
...MySQL 6.0.2 with Falcon on Linux with Debian 4.
I have compiled the source code for 64 bit executable.
The system is an Intel 2 cpus 4 cores each, with 8 GB
of RAM.
After having created
approximately 8,500 empty tables mysqld server was
still alive, you could
I have re-run and job and I was able to repeat the
problem.
Find attached the mysql server error log with all the
tarces.
Could you please help ?
Thanks,
Mariella
--- Mariella Petrini [EMAIL PROTECTED]
wrote:
Hi All,
I have started using MySQL 6.0.2 with Falcon on
Linux
with Debian
I never tried the falcon engine, but could it be that mysql is running
out of file descriptor ?
I think debian is limited to something around 8k per user by default.
Check your pam settings and your ulimit ... Database usually use a lot
of file handle and it's generally safe to increase it.
If Debian is limited to create files over 8k, it can be the reason of the
problem.
Falcon seems not create data file for tables, but still create .frm files
for each tables.
--
Jaemyung Kim
2007/9/9, Mathieu Bruneau [EMAIL PROTECTED]:
I never tried the falcon engine, but could it be that
I don't think that is the problem.
I have been able to create over a 1,000,000 of tables with MySQL 5.1.21 and
different storage engines with the same environment (I had already ulimit set).
Thanks,
Mariella
Mathieu Bruneau [EMAIL PROTECTED] wrote: I never tried the falcon engine, but
could
