Gleb
- Original Message -
> Hello.
>
>
> >Does that imply that if we set this flush_time value to zero (ie no
> >periodic flush to disk), then some of the data will not be committed to
> >disk, and if we had a subsequent power failure, then any data since the
> >last flush would be lost
Hello.
>Does that imply that if we set this flush_time value to zero (ie no
>periodic flush to disk), then some of the data will not be committed to
>disk, and if we had a subsequent power failure, then any data since the
>last flush would be lost? We have innodb_flush_log_at_trx_commit set
We're running mostly with InnoDB tables, about 5% updates/inserts/deletes,
the rest selects, on Windows NT.
In setting table_cache to 256 from the default 64, we hoped to improve
performance a little, by not having to continually close/open tables.
Then we noticed that the opened table count d
