[MDEV-6948] SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id) - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Duplicate
Affects Version/s: N/A
Fix Version/s: 10.1.2
Component/s: Admin statements
Labels:
None

Description

Test case
--source include/have_log_bin.inc

create table t1 (i int);
set gtid_domain_id = 10;
insert into t1 values (1),(2);
set statement gtid_domain_id = 20 for insert into t1 values (3),(4);
show binlog events;

drop table t1;

Binary log
show binlog events;
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000001 4 Format_desc 1 248 Server ver: 10.1.1-MariaDB-wsrep-debug-log, Binlog ver: 4
master-bin.000001 248 Gtid_list 1 273 []
master-bin.000001 273 Binlog_checkpoint 1 313 master-bin.000001
master-bin.000001 313 Gtid 1 351 GTID 0-1-1
master-bin.000001 351 Query 1 437 use `test`; create table t1 (i int)
master-bin.000001 437 Gtid 1 475 BEGIN GTID 10-1-1
master-bin.000001 475 Query 1 567 use `test`; insert into t1 values (1),(2)
master-bin.000001 567 Query 1 636 COMMIT
master-bin.000001 636 Gtid 1 674 BEGIN GTID 10-1-2
master-bin.000001 674 Query 1 804 use `test`; set statement gtid_domain_id = 20 for insert into t1 values (3),(4)
master-bin.000001 804 Query 1 873 COMMIT

bb-10.1-set-statement tree
commit e64f5d8f758bcc1a8856ba9fba01780533f80747
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Sun Oct 26 16:27:54 2014 +0100

Fixed test suite global variable saving

Same is true for other variables that participate in GTID generation – gtid_seq_no and server_id.

Attachments

Issue Links

relates to

MDEV-5231 Per query variables from Percona Server [patch]

Closed

MDEV-6923 Testing for SET STATEMENT .. FOR (MDEV-5231, per-query variables)

Closed

Activity

Ascending order - Click to sort in descending order

Elena Stepanova created issue - 2014-10-27 13:18

Elena Stepanova made changes - 2014-10-27 13:18

Field	Original Value	New Value
Link		This issue relates to ~~MDEV-6923~~ [ ~~MDEV-6923~~ ]

Elena Stepanova made changes - 2014-10-27 13:18

Link

This issue relates to ~~MDEV-5231~~ [ ~~MDEV-5231~~ ]

Elena Stepanova made changes - 2014-10-27 13:26

Description

{code:title=Test case}
--source include/have_log_bin.inc

create table t1 (i int);
set gtid_domain_id = 10;
insert into t1 values (1),(2);
set statement gtid_domain_id = 20 for insert into t1 values (3),(4);
show binlog events;

drop table t1;
{code}

{noformat:title=Binary log}
show binlog events;
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000001 4 Format_desc 1 248 Server ver: 10.1.1-MariaDB-wsrep-debug-log, Binlog ver: 4
master-bin.000001 248 Gtid_list 1 273 []
master-bin.000001 273 Binlog_checkpoint 1 313 master-bin.000001
master-bin.000001 313 Gtid 1 351 GTID 0-1-1
master-bin.000001 351 Query 1 437 use `test`; create table t1 (i int)
master-bin.000001 437 Gtid 1 475 BEGIN GTID 10-1-1
master-bin.000001 475 Query 1 567 use `test`; insert into t1 values (1),(2)
master-bin.000001 567 Query 1 636 COMMIT
master-bin.000001 636 Gtid 1 674 BEGIN GTID 10-1-2
master-bin.000001 674 Query 1 804 use `test`; set statement gtid_domain_id = 20 for insert into t1 values (3),(4)
master-bin.000001 804 Query 1 873 COMMIT
{noformat}

{noformat}
commit e64f5d8f758bcc1a8856ba9fba01780533f80747
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Sun Oct 26 16:27:54 2014 +0100

Fixed test suite global variable saving
{noformat}

{code:title=Test case}
--source include/have_log_bin.inc

create table t1 (i int);
set gtid_domain_id = 10;
insert into t1 values (1),(2);
set statement gtid_domain_id = 20 for insert into t1 values (3),(4);
show binlog events;

drop table t1;
{code}

{noformat:title=Binary log}
show binlog events;
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000001 4 Format_desc 1 248 Server ver: 10.1.1-MariaDB-wsrep-debug-log, Binlog ver: 4
master-bin.000001 248 Gtid_list 1 273 []
master-bin.000001 273 Binlog_checkpoint 1 313 master-bin.000001
master-bin.000001 313 Gtid 1 351 GTID 0-1-1
master-bin.000001 351 Query 1 437 use `test`; create table t1 (i int)
master-bin.000001 437 Gtid 1 475 BEGIN GTID 10-1-1
master-bin.000001 475 Query 1 567 use `test`; insert into t1 values (1),(2)
master-bin.000001 567 Query 1 636 COMMIT
master-bin.000001 636 Gtid 1 674 BEGIN GTID 10-1-2
master-bin.000001 674 Query 1 804 use `test`; set statement gtid_domain_id = 20 for insert into t1 values (3),(4)
master-bin.000001 804 Query 1 873 COMMIT
{noformat}

{noformat:title=bb-10.1-set-statement tree}
commit e64f5d8f758bcc1a8856ba9fba01780533f80747
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Sun Oct 26 16:27:54 2014 +0100

Fixed test suite global variable saving
{noformat}

Elena Stepanova made changes - 2014-10-27 13:51

Summary

SET STATEMENT gtid_domain_id = ... FOR has no effect

SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id)

Elena Stepanova made changes - 2014-10-27 13:52

Description

{code:title=Test case}
--source include/have_log_bin.inc

create table t1 (i int);
set gtid_domain_id = 10;
insert into t1 values (1),(2);
set statement gtid_domain_id = 20 for insert into t1 values (3),(4);
show binlog events;

drop table t1;
{code}

{noformat:title=Binary log}
show binlog events;
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000001 4 Format_desc 1 248 Server ver: 10.1.1-MariaDB-wsrep-debug-log, Binlog ver: 4
master-bin.000001 248 Gtid_list 1 273 []
master-bin.000001 273 Binlog_checkpoint 1 313 master-bin.000001
master-bin.000001 313 Gtid 1 351 GTID 0-1-1
master-bin.000001 351 Query 1 437 use `test`; create table t1 (i int)
master-bin.000001 437 Gtid 1 475 BEGIN GTID 10-1-1
master-bin.000001 475 Query 1 567 use `test`; insert into t1 values (1),(2)
master-bin.000001 567 Query 1 636 COMMIT
master-bin.000001 636 Gtid 1 674 BEGIN GTID 10-1-2
master-bin.000001 674 Query 1 804 use `test`; set statement gtid_domain_id = 20 for insert into t1 values (3),(4)
master-bin.000001 804 Query 1 873 COMMIT
{noformat}

{noformat:title=bb-10.1-set-statement tree}
commit e64f5d8f758bcc1a8856ba9fba01780533f80747
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Sun Oct 26 16:27:54 2014 +0100

Fixed test suite global variable saving
{noformat}

{code:title=Test case}
--source include/have_log_bin.inc

create table t1 (i int);
set gtid_domain_id = 10;
insert into t1 values (1),(2);
set statement gtid_domain_id = 20 for insert into t1 values (3),(4);
show binlog events;

drop table t1;
{code}

{noformat:title=Binary log}
show binlog events;
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000001 4 Format_desc 1 248 Server ver: 10.1.1-MariaDB-wsrep-debug-log, Binlog ver: 4
master-bin.000001 248 Gtid_list 1 273 []
master-bin.000001 273 Binlog_checkpoint 1 313 master-bin.000001
master-bin.000001 313 Gtid 1 351 GTID 0-1-1
master-bin.000001 351 Query 1 437 use `test`; create table t1 (i int)
master-bin.000001 437 Gtid 1 475 BEGIN GTID 10-1-1
master-bin.000001 475 Query 1 567 use `test`; insert into t1 values (1),(2)
master-bin.000001 567 Query 1 636 COMMIT
master-bin.000001 636 Gtid 1 674 BEGIN GTID 10-1-2
master-bin.000001 674 Query 1 804 use `test`; set statement gtid_domain_id = 20 for insert into t1 values (3),(4)
master-bin.000001 804 Query 1 873 COMMIT
{noformat}

{noformat:title=bb-10.1-set-statement tree}
commit e64f5d8f758bcc1a8856ba9fba01780533f80747
Author: Oleksandr Byelkin <sanja@mariadb.com>
Date: Sun Oct 26 16:27:54 2014 +0100

Fixed test suite global variable saving
{noformat}

Same is true for other variables that participate in GTID generation -- {{gtid_seq_no}} and {{server_id}}.

Oleksandr Byelkin added a comment - 2014-10-29 11:30

The variable is prohibited in SET STATEMENT for now.

Oleksandr Byelkin added a comment - 2014-10-29 11:30 The variable is prohibited in SET STATEMENT for now.

Elena Stepanova added a comment - 2014-11-03 01:38

What about gtid_seq_no and server_id?

Interestingly, it works for DDL, but not for DML:

MariaDB [test]> set statement gtid_seq_no = 11, server_id = 111 for create table t1 (i int);

Query OK, 0 rows affected (1.07 sec)

MariaDB [test]> set statement gtid_seq_no = 22, server_id = 222 for insert into t1 values (1);

Query OK, 1 row affected (0.08 sec)

MariaDB [test]> show binlog events;

...

| wheezy-64-bin.000001 | 468 | Gtid              |       111 |         506 | GTID 0-111-11                                                                             |

| wheezy-64-bin.000001 | 506 | Query             |       111 |         644 | use `test`; set statement gtid_seq_no = 11, server_id = 111 for create table t1 (i int)   |

| wheezy-64-bin.000001 | 644 | Gtid              |         2 |         682 | BEGIN GTID 0-2-12                                                                         |

| wheezy-64-bin.000001 | 682 | Query             |       222 |         822 | use `test`; set statement gtid_seq_no = 22, server_id = 222 for insert into t1 values (1) |

| wheezy-64-bin.000001 | 822 | Xid               |         2 |         849 | COMMIT /* xid=465 */                                                                      |

...

Elena Stepanova added a comment - 2014-11-03 01:38 What about gtid_seq_no and server_id? Interestingly, it works for DDL, but not for DML: MariaDB [test]> set statement gtid_seq_no = 11, server_id = 111 for create table t1 (i int ); Query OK, 0 rows affected (1.07 sec) MariaDB [test]> set statement gtid_seq_no = 22, server_id = 222 for insert into t1 values (1); Query OK, 1 row affected (0.08 sec) MariaDB [test]> show binlog events; ... | wheezy-64-bin.000001 | 468 | Gtid | 111 | 506 | GTID 0-111-11 | | wheezy-64-bin.000001 | 506 | Query | 111 | 644 | use `test`; set statement gtid_seq_no = 11, server_id = 111 for create table t1 (i int) | | wheezy-64-bin.000001 | 644 | Gtid | 2 | 682 | BEGIN GTID 0-2-12 | | wheezy-64-bin.000001 | 682 | Query | 222 | 822 | use `test`; set statement gtid_seq_no = 22, server_id = 222 for insert into t1 values (1) | | wheezy-64-bin.000001 | 822 | Xid | 2 | 849 | COMMIT /* xid=465 */ | ...

Oleksandr Byelkin added a comment - 2014-11-11 13:08

Here (as well as all bugs connected to binlog) cause is that we write binlog after restoring variables values.

Oleksandr Byelkin added a comment - 2014-11-11 13:08 Here (as well as all bugs connected to binlog) cause is that we write binlog after restoring variables values.

Oleksandr Byelkin made changes - 2014-11-28 17:47

Status

Open [ 1 ]

In Progress [ 3 ]

Oleksandr Byelkin made changes - 2014-11-28 18:25

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Oleksandr Byelkin added a comment - 2014-11-28 18:26

duplicate of 7006

Oleksandr Byelkin added a comment - 2014-11-28 18:26 duplicate of 7006

Oleksandr Byelkin made changes - 2014-11-28 18:26

Fix Version/s		10.1.2 [ 15801 ]
Fix Version/s	10.1 [ 16100 ]
Resolution		Duplicate [ 3 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2015-02-02 21:46

Component/s		Admin statements [ 11400 ]
Component/s	OTHER [ 10125 ]

Rasmus Johansson (Inactive) made changes - 2015-05-18 17:50

Workflow

MariaDB v2 [ 56600 ]

MariaDB v3 [ 61368 ]

Sergei Golubchik made changes - 2021-12-06 21:40

Workflow

MariaDB v3 [ 61368 ]

MariaDB v4 [ 148356 ]

People

Assignee:: Oleksandr Byelkin

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2014-10-27 13:18

Updated:: 2015-03-12 09:19

Resolved:: 2014-11-28 18:26

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration