Issue created as MDEV-25358.
-----Original Message----- From: Maria-discuss [mailto:maria-discuss- bounces+viper=vipernet.hu@lists.launchpad.net] On Behalf Of Dajka Tamás Sent: Wednesday, April 7, 2021 3:18 PM To: 'Sergei Golubchik' <serg@mariadb.org> Cc: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] MEMORY tables and binlog
Hi Sergei!
Sure, I'll report it. Yes, I think it's correctly reproducable.
Cheers,
Tom
-----Original Message----- From: Sergei Golubchik [mailto:serg@mariadb.org] Sent: Wednesday, April 7, 2021 3:11 PM To: Dajka Tamás <viper@vipernet.hu> Cc: maria-discuss@lists.launchpad.net Subject: Re: [Maria-discuss] MEMORY tables and binlog
Hi, Dajka!
This looks like a bug. Could you report it at jira.mariadb.org? Do you know when it happen, can you reproduce it at will?
On Apr 07, Dajka Tamás wrote:
Hi All,
When checking the binlog on the new-node01 with mysqlbinlog, I get the following:
# at 2361 #210407 11:13:34 server id 4 end_log_pos 2403 CRC32 0x90080d27 GTID 100-4-37336878143 trans /*!100001 SET @@session.gtid_seq_no=37336878143*//*!*/; START TRANSACTION /*!*/; # at 2403 #210407 11:13:34 server id 4 end_log_pos 2527 CRC32 0x27183d2f Query thread_id=341297541 exec_time=318 error_code=0 SET TIMESTAMP=1617786814/*!*/; DELETE FROM `mydb1`.`collect_output`e<FB>#<98> /*!*/; # at 2527 #210407 11:13:34 server id 4 end_log_pos 2598 CRC32 0x427f0ed7 Table_map: `mydb1`.`collect_output` mapped to number 1330
Is this a bug or a known issue? Is there any other way to solve this, than exclude the MEMORY tables from the replication?
Regards, Sergei VP of MariaDB Server Engineering and security@mariadb.org
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp