Dear Alec Thanks for the quick response.
I am doing some work in High Availabilty. We have two real servers(just 2 PC's) and we want the both PC to run MySQL but uses one common database data file. We have one NAS server, we will keep all the data file there and mount it on local system and try the MySQL, things are half way done I mean I am able to access the data files, table and now its data too but the problem its not writing in file at the same time and there are some problem in closing the files. When I checking the table using 'myisamchk' it show the below results:- ***************************************************************************** Checking MyISAM file: pi_dispatcher.MYI Data records: 3 Deleted blocks: 0 myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference MyISAM-table 'pi_dispatcher.MYI' is usable but should be fixed ***************************************************************************** My problem is I want the MySQL will write all the data in the file after every command and close the files properly, nothing in buffers and cache. How can we do that, I tried with --flush but its not helping much, is there any good options? regards bhartendu On Sat, 2003-12-06 at 20:15, [EMAIL PROTECTED] wrote: > > > > > > > > Bhartendu Maheshwari <[EMAIL PROTECTED]> wrote on 06/12/2003 > 14:40:29: > > > I know at the time of table creation mysql creates 3 file .frm, .MYD, > > .MYI and is stored in the path given by --datadir=****, I want to know > > when I call insert row then where is this data goes I mean in which file > > it stores. I want to shared the database files but when I do this it > > shares only the table definition not the table data, shows tables are > > empty. So can anyone please help in sharing the table data. > > The table definition is in the .frm file, the raw table data in the .MYD > file and the indexes in the .MYI file. > > HOWEVER, it is very dangerous to share these files. MySQL performs > extensive internal caching, so that it is rarely possible to know when > these files are up-to-date while mysqld is running. Sharing the data files, > rather than sharing the mysqld server, is not to be recommended at all. > > Could you perhaps explain what you are trying to achieve? There is quite > likely to be a better way to achieve it. > > Alec > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
