"MaFai" <[EMAIL PROTECTED]> wrote:
> Hello, Victoria Reznichenko,
> 
> The p_showing table,the following is the create table sql statement.
> 
> 
> | p_showing | CREATE TABLE `p_showing` (
>  `showing_timestamp` timestamp(14) NOT NULL,
>  `showing_channel_name` varchar(50) NOT NULL default '',
>  `showing_asset_name` varchar(50) NOT NULL default '',
>  `showing_start_time` datetime default NULL,
>  `showing_keywords` varchar(100) default NULL,
>  `showing_ip` varchar(15) NOT NULL default '',
>  `showing_port` varchar(10) NOT NULL default '',
>  `showing_end_time` datetime default NULL,
>  `showing_resource` varchar(20) NOT NULL default '',
>  `showing_status` varchar(20) NOT NULL default '',
>  `showing_AutoDelte` varchar(5) NOT NULL default '',
>  `showing_Feed` varchar(20) NOT NULL default '',
>  `showing_Interactive_Control` varchar(5) NOT NULL default '',
>  `showing_start_time_ctime` datetime default NULL,
>  `showing_end_time_ctime` datetime default NULL,
>  `showing_URL` varchar(100) NOT NULL default '',
>  `source_ip` varchar(15) default NULL
> ) TYPE=HEAP |
> 
> Mysql Version
> 
> 
> mysqladmin  Ver 8.40 Distrib 4.0.12, for pc-linux on i686
> Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult AB
> This software comes with ABSOLUTELY NO WARRANTY. This is free software,
> and you are welcome to modify and redistribute it under the GPL license
> 
> Server version          4.0.12-standard-log
> Protocol version        10
> Connection              Localhost via UNIX socket
> UNIX socket             /tmp/mysql.sock
> Uptime:                 1 day 5 hours 9 min 2 sec
> 
> Threads: 4  Questions: 1005973  Slow queries: 22  Opens: 102  Flush tables: 1  Open 
> tables: 78  Queries per second avg: 9.586
> 

I tested using your table structure and replication worked well. Please, upgrade MySQL 
server to 4.0.16 and let me know if the problem still exists.

> 
> 
> 
> ======= At 2003-11-03, 14:51:00 you wrote: =======
> 
>>"MaFai" <[EMAIL PROTECTED]> wrote:
>>> Hello, mysql,
>>> 
>>> The replication running smoothly between the master and slave,except that the heap 
>>> table can not be synchronized.
>>> 
>>> While the master insert the record into the heap table,the slave would do the same 
>>> job.
>>> While the master delete the record in the heap table,the slave wouldn't do so.
>>> After serval days passed,the heap table would overloading in the slave,because it 
>>> never delete the record in heap table.
>>> 
>>> The mysql seems doesn't support heap table in replication,right?
>>> If yes,i should change the table type to innodb,although it would lose the 
>>> performance.
>>> 
>>> The manaul doesn't mention this.
>>> 
>>> Any idea apprecated.
>>> 
>>> Env:Mysql 4.0,Linux Red Hat7,256mb ram.
>>> 
>>
>>What exactly version of MySQL do you use? I tested replication with HEAP tables and 
>>all worked like a charm. Could you provide a test case?


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Victoria Reznichenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
       <___/   www.mysql.com





-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to