This is actually a bug https://mariadb.atlassian.net/browse/MDEV-5719.
Pavel
On Fri, May 23, 2014 at 11:18 AM, Charles Cazabon
wrote:
> Greetings,
>
> I recently upgraded the db server behind an application from MySQL 5.1.73 (as
> shipped in Ubuntu 10.04 "Lucid") to MariaDB 10.0.11 (from the Mar
I personally would prefer if MariaDB had performance schema not
compiled in by default. Then we wouldn't be frustrated every time we
upgrade and find out that the tarball doesn't compile without
performance schema (yes, 10.0.11 doesn't compile).
On Tue, Jun 3, 2014 at 1:20 AM, Colin Charles wrote
On Wed, Jun 11, 2014 at 8:32 PM, Roberto Spadim wrote:
> Guys, i'm with a "newbie" question
> I need to swap a primary key value, for example:
> create table test (
> id int not null default 0,
> other varchar(255) not null default '',
> primary key(id)
> );
> insert into test (1,'a');
> inser
with a innodb/transactional table
> what about a aria/myisam/connect/federated table?
>
>
> 2014-06-12 0:45 GMT-03:00 Pavel Ivanov :
>
>> On Wed, Jun 11, 2014 at 8:32 PM, Roberto Spadim
>> wrote:
>> > Guys, i'm with a "newbie" question
>> &g
7; then '1'
>>>> end;
>>>> /* Erro SQL (1062): Duplicate entry '2' for key 'PRIMARY' */
>>>>
>>>>
>>>>
>>>> 2014-06-12 1:26 GMT-03:00 Roberto Spadim :
>>>>
>>>>> that
/7b96c34bb6e79ace33e56627672b98a5
>
> Joseph Glanville
> Sent from Polymail
> <https://polymail.io/?utm_source=polymail&utm_medium=referral&utm_campaign=signature>
>
>
> On Fri, 29 Jul 2016 at 3:08 PM Pavel Ivanov > wrote:
>
>> By "binlog filename ch
wledge the write and falls back to async only to immediately
> re-establish semi-sync replication. It does this every time the master
> begins writing to a new binlog.
>
>
> Joseph.
> --
> *From:* Justin Swanhart
> *Sent:* Friday, 29 July 2016
ng xtrabackup.
>
> Update slave GTID position using information returned from xtrabackup
>
> Connect the slave using GTID
>
> Insert some data, check that data is replicating correctly to slave.
>
> Keep inserting data until binlog rolls over.
>
> Note that inserts no
binlog code to do much
> more debugging.
>
>
> Joseph.
>
>
> From: Pavel Ivanov
> Sent: Saturday, 13 August 2016 2:17:39 PM
> To: Joseph Glanville; Kristian Nielsen
> Cc: maria-discuss@lists.launchpad.net; Will Fong
>
> Subject: Re:
idn't include it in
https://jira.mariadb.org/browse/MDEV-7257.
On Mon, Aug 15, 2016 at 5:05 AM, Kristian Nielsen
wrote:
> Pavel Ivanov writes:
>
>> binlog ending at position mariadb-bin.04:2039896, somehow the
>> function ReplSemiSyncMaster::commitTrx() gets trx_wait_binlog_n
> For example, in MariaDB one can use InnoDB
> for system tables too. Always could, even in 5.5, it's not a new
> feature. There is no code that limits system tables to a specific
> storage engine.
This is not true even in MariaDB 10.2:
https://github.com/MariaDB/server/blob/10.2/storage/innobase/
There is no way to find corresponding binlog file and position on the
slave. You should use GTIDs to find corresponding binlog positions.
On Thu, Nov 17, 2016 at 7:19 PM, Ljr Yang wrote:
>
> Hi,
>we config master slave and set log_slave_updates = 1 on slave.
>on master server‘s binlog fi
nly filter GTID 0-118-60061898358 in all binlog file of slave ?
>
> mysqlbinlog -vv mysqbin.01 | grep -B5 "0-118-60061898358"
> mysqlbinlog -vv mysqbin.02 | grep -B5 "0-118-60061898358"
>
>
> 2016-11-18 13:24 GMT+08:00 Pavel Ivanov :
>>
>
:04 AM, Artem Kuchin wrote:
> I understand that. I don't understand how it happened that table schema on
> slave is not the same
> as on master. Any idea?
>
> 29.11.2016 19:42, Pavel Ivanov пишет:
>
>> You really need to make schema of this table to be the sam
Could it be that your slaves are periodically disconnecting from the
master and then reconnecting again, and you just happened to catch a
state when only one slave is connected when you queried for
Rpl_semi_sync_master_clients status? To confirm or deny this you
should look at the master's error lo
4 [ERROR] Read semi-sync reply network
>> error: (errno: 1158)
>> 2017-03-28 18:07:07 140469136173824 [Note] Stop semi-sync binlog_dump to
>> slave (server_id: 63)
>> 2017-03-28 18:09:14 140467881470720 [Note] Start semi-sync binlog_dump to
>> slave (server_id: 63), po
https://mariadb.com/kb/en/mariadb/annotate_rows_log_event/
On Fri, Jun 9, 2017 at 11:05 AM, Justin Swanhart wrote:
> Hi,
>
> I seem to recall reading that MariaDB can annotate the binary log with the
> original SQL statement for a given set of ROW changes in the binary log, but
> I can't seem to
Note that several system tables in "mysql" schema cannot have InnoDB
as storage engine due to explicit prohibition in the InnoDB code (see
https://github.com/MariaDB/server/blob/10.4/storage/innobase/row/row0mysql.cc#L2376)
and due to lots of other code throughout the codebase assuming that
the sys
row from being written again? Also, when talking about
> large tables, could this "table bloat" impact performance in, for instance,
> sequential scans?
>
> Thanks again,
> Arlindo Neto.
>
> Em sex, 27 de jul de 2018 às 18:35, Pavel Ivanov
> escreveu:
>>
19 matches
Mail list logo
