[MDEV-4989] Support for GTID in mysqlbinlog - Jira

Kristian Nielsen created issue - 2013-09-03 15:38

Sergei Golubchik made changes - 2014-03-06 10:31

Field	Original Value	New Value
Description	The mysqlbinlog client program needs to be updated to support GTID. At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server. Also, mysqlbinlog should put at the end of the dump the statement SET session.server_id = @@global.server_id, session.gtid_domain_id=@@global.gtid_domain_id at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.	The mysqlbinlog client program needs to be updated to support GTID. At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server. Also, mysqlbinlog should put at the end of the dump the statement {code:sql} SET session.server_id = @@global.server_id, session.gtid_domain_id=@@global.gtid_domain_id {code} at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.

Sergei Golubchik made changes - 2014-03-06 10:53

Labels

gtid

gsoc14 gtid

Sergei Golubchik made changes - 2014-03-06 11:02

Assignee

Kristian Nielsen [ knielsen ]

Sergei Golubchik made changes - 2014-03-06 11:02

Fix Version/s

10.1.0 [ 12200 ]

Sergei Golubchik made changes - 2014-03-06 11:03

Issue Type

Bug [ 1 ]

Task [ 3 ]

Sergei Golubchik made changes - 2014-03-06 11:03

Description

The mysqlbinlog client program needs to be updated to support GTID.

At least it should be possible to start and stop the dump from given GTID
positions. Both when reading binlog files off-line and when connecting to a
running server.

Also, mysqlbinlog should put at the end of the dump the statement
{code:sql}
SET session.server_id = @@global.server_id,
session.gtid_domain_id=@@global.gtid_domain_id
{code}
at the end to reduce the risk of those session variables incorrectly spilling
into subsequent statements run in the same session.

The mysqlbinlog client program needs to be updated to support GTID.

At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server.

Also, mysqlbinlog should put at the end of the dump the statement
{code:sql}
SET session.server_id = @@global.server_id,
session.gtid_domain_id=@@global.gtid_domain_id
{code}
at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.

Kristian Nielsen made changes - 2014-03-06 12:07

Description

The mysqlbinlog client program needs to be updated to support GTID.

At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server.

Also, mysqlbinlog should put at the end of the dump the statement
{code:sql}
SET session.server_id = @@global.server_id,
session.gtid_domain_id=@@global.gtid_domain_id
{code}
at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.

The mysqlbinlog client program needs to be updated to support GTID.

At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server.

Also, mysqlbinlog should put at the end of the dump the statement
{code:sql}
SET session.server_id = @@global.server_id,
session.gtid_domain_id=@@global.gtid_domain_id
{code}
at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.

I think, the first step should be to make a list over all the ways that
mysqlbinlog currently processes old-style binlog positions (file+offset) in
any way. And then make suggestions for how mysqlbinlog should do the similar
task with GTID.

Sergei Golubchik made changes - 2014-04-17 12:01

Labels

gsoc14 gtid

gsoc14 gtid replication

Colin Charles made changes - 2014-05-04 07:40

Labels

gsoc14 gtid replication

gsoc14 gtid mysqlbinlog replication

Daniel Bartholomew made changes - 2014-05-16 12:59

Assignee

Kristian Nielsen [ knielsen ]

Daniel Bartholomew made changes - 2014-05-16 12:59

Priority

Major [ 3 ]

Minor [ 4 ]

Sergei Golubchik made changes - 2014-06-13 15:06

Workflow

defaullt [ 28813 ]

MariaDB v2 [ 43761 ]

Sergei Golubchik made changes - 2014-06-30 01:16

Fix Version/s		10.1 [ 16100 ]
Fix Version/s	10.1.0 [ 12200 ]

Kristian Nielsen made changes - 2014-06-30 15:01

Priority

Minor [ 4 ]

Critical [ 2 ]

Kristian Nielsen added a comment - 2014-06-30 15:03

This is actually a really good starter project for someone to get into working with the GTID code.

The tasks requires getting some moderate understanding on how GTID works in general, but the actual code that needs to be worked on is fairly isolated and doesn't need to touch a majority of the GTID and replication stuff.

Kristian Nielsen added a comment - 2014-06-30 15:03 This is actually a really good starter project for someone to get into working with the GTID code. The tasks requires getting some moderate understanding on how GTID works in general, but the actual code that needs to be worked on is fairly isolated and doesn't need to touch a majority of the GTID and replication stuff.

Kristian Nielsen made changes - 2014-09-01 14:35

Priority

Critical [ 2 ]

Minor [ 4 ]

Kristian Nielsen made changes - 2014-10-13 14:07

Fix Version/s

10.1 [ 16100 ]

Sergei Golubchik made changes - 2014-11-07 16:35

Fix Version/s

10.2.0 [ 14601 ]

Sergei Golubchik made changes - 2015-02-07 13:49

Labels

gsoc14 gtid mysqlbinlog replication

gsoc14 gsoc15 gtid mysqlbinlog replication

Kristian Nielsen made changes - 2015-03-16 10:06

Description

The mysqlbinlog client program needs to be updated to support GTID.

At least it should be possible to start and stop the dump from given GTID positions. Both when reading binlog files off-line and when connecting to a running server.

Also, mysqlbinlog should put at the end of the dump the statement
{code:sql}
SET session.server_id = @@global.server_id,
session.gtid_domain_id=@@global.gtid_domain_id
{code}
at the end to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session.

I think, the first step should be to make a list over all the ways that
mysqlbinlog currently processes old-style binlog positions (file+offset) in
any way. And then make suggestions for how mysqlbinlog should do the similar
task with GTID.

The mysqlbinlog client program needs to be updated to support GTID.

Here is a suggested list of things to be done:

- The --start-position and --stop-position options should be able to take
   GTID positions; or maybe there should be new --start-gtid and --stop-gtid
   options. Like "--start-gtid=0-1-100,1-2-200,2-1-1000".

- A GTID position means the point just _after_ that GTID. So starting from
   GTID 0-1-100 and stopping at GTID 0-1-200, the first GTID output will
   probably be 0-1-101 and the last one 0-1-200. Note that if some domain is
   not specified in the position, it means to start from the begining,
   respectively stop immediately in that domain.

- Starting and stopping GTID should work both with local files, and with
   --read-from-remote-server. For the latter, there are a couple of extra
   things that need doing in the master-slave protocol, see
   get_master_version_and_clock() in sql/slave.cc.

- At the end of the dump, put these statements, to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session:
   SET session.server_id = @@global.server_id,
       session.gtid_domain_id=@@global.gtid_domain_id;

Probably some more things will come up during the work, but this looks like a
reasonable start.

Kristian Nielsen added a comment - 2015-03-16 10:08

Some suggestions for getting started with this:

I would recommend to start by reading the GTID documentation, and
experimenting with all the relevant features described there, to familiarise
yourself with it. The main thing is to understand the concept of GTID position
and binlog order, and the relation to replication domains:

https://mariadb.com/kb/en/mariadb/global-transaction-id/

There are also some blog posts:

http://kristiannielsen.livejournal.com/16826.html
http://kristiannielsen.livejournal.com/17008.html
http://kristiannielsen.livejournal.com/17238.html

And similarly, familiarise yourself with mysqlbinlog and how it would make
sense for it to be extended to support GTID.

Then make a detailed proposal for how the user-visible interface of
mysqlbinlog should be extended, and send it to the list for comments.

The next step will be to understand the concept of binlog state
(@@gtid_binlog_state), and how it is used to deal correctly with out-of-order
GTID sequence numbers in binlogs. This is mostly an internal implementation
detail, but necessary to be able to correctly identify starting and stopping
GTID positions in all cases.

Kristian Nielsen added a comment - 2015-03-16 10:08 Some suggestions for getting started with this: I would recommend to start by reading the GTID documentation, and experimenting with all the relevant features described there, to familiarise yourself with it. The main thing is to understand the concept of GTID position and binlog order, and the relation to replication domains: https://mariadb.com/kb/en/mariadb/global-transaction-id/ There are also some blog posts: http://kristiannielsen.livejournal.com/16826.html http://kristiannielsen.livejournal.com/17008.html http://kristiannielsen.livejournal.com/17238.html And similarly, familiarise yourself with mysqlbinlog and how it would make sense for it to be extended to support GTID. Then make a detailed proposal for how the user-visible interface of mysqlbinlog should be extended, and send it to the list for comments. The next step will be to understand the concept of binlog state (@@gtid_binlog_state), and how it is used to deal correctly with out-of-order GTID sequence numbers in binlogs. This is mostly an internal implementation detail, but necessary to be able to correctly identify starting and stopping GTID positions in all cases.

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

Workflow

MariaDB v2 [ 43761 ]

MariaDB v3 [ 65819 ]

Sergei Golubchik made changes - 2015-11-17 17:31

Fix Version/s

10.2 [ 14601 ]

Sergei Golubchik made changes - 2016-01-15 15:48

Fix Version/s

10.2 [ 14601 ]

Sergei Golubchik made changes - 2016-01-15 20:21

Description

The mysqlbinlog client program needs to be updated to support GTID.

Here is a suggested list of things to be done:

- The --start-position and --stop-position options should be able to take
   GTID positions; or maybe there should be new --start-gtid and --stop-gtid
   options. Like "--start-gtid=0-1-100,1-2-200,2-1-1000".

- A GTID position means the point just _after_ that GTID. So starting from
   GTID 0-1-100 and stopping at GTID 0-1-200, the first GTID output will
   probably be 0-1-101 and the last one 0-1-200. Note that if some domain is
   not specified in the position, it means to start from the begining,
   respectively stop immediately in that domain.

- Starting and stopping GTID should work both with local files, and with
   --read-from-remote-server. For the latter, there are a couple of extra
   things that need doing in the master-slave protocol, see
   get_master_version_and_clock() in sql/slave.cc.

- At the end of the dump, put these statements, to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session:
   SET session.server_id = @@global.server_id,
       session.gtid_domain_id=@@global.gtid_domain_id;

Probably some more things will come up during the work, but this looks like a
reasonable start.

The mysqlbinlog client program needs to be updated to support GTID.

Here is a suggested list of things to be done:

- The {{\-\-start-position}} and {{\-\-stop-position}} options should be able to take
   GTID positions; or maybe there should be new {{\-\-start-gtid}} and {{\-\-stop-gtid}}
   options. Like {{--start-gtid=0-1-100,1-2-200,2-1-1000}}.

- A GTID position means the point just _after_ that GTID. So starting from
   GTID 0-1-100 and stopping at GTID 0-1-200, the first GTID output will
   probably be 0-1-101 and the last one 0-1-200. Note that if some domain is
   not specified in the position, it means to start from the begining,
   respectively stop immediately in that domain.

- Starting and stopping GTID should work both with local files, and with
   {{--read-from-remote-server}}. For the latter, there are a couple of extra
   things that need doing in the master-slave protocol, see
   {{get_master_version_and_clock()}} in {{sql/slave.cc}}.

- At the end of the dump, put these statements, to reduce the risk of those session variables incorrectly spilling into subsequent statements run in the same session:
{code:sql}
   SET session.server_id = @@global.server_id,
       session.gtid_domain_id=@@global.gtid_domain_id;
{code}
Probably some more things will come up during the work, but this looks like a
reasonable start.

Colin Charles made changes - 2016-02-18 12:00

Labels

gsoc14 gsoc15 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gtid mysqlbinlog replication

Frederik Brinck Jensen added a comment - 2016-03-19 17:15

Hi Kristian,

You have logged this issue/idea to four weeks only. Do you recommend GSoC applicants to propose to take on other ideas as well, or elaborate on this one, considering that they might finish this implementation within the estimated time.

Thanks in advance,
Frederik

Frederik Brinck Jensen added a comment - 2016-03-19 17:15 Hi Kristian, You have logged this issue/idea to four weeks only. Do you recommend GSoC applicants to propose to take on other ideas as well, or elaborate on this one, considering that they might finish this implementation within the estimated time. Thanks in advance, Frederik

Sergei Golubchik made changes - 2017-02-11 18:07

Labels

gsoc14 gsoc15 gsoc16 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gsoc17 gtid mysqlbinlog replication

Sergei Golubchik made changes - 2017-03-01 22:04

Fix Version/s

10.2 [ 14601 ]

Sergei Golubchik made changes - 2017-03-01 22:04

Assignee

Kristian Nielsen [ knielsen ]

Amol Holani added a comment - 2017-03-12 07:04

Hi Kristian,
I'm a senior year undergraduate student majoring in Computer Science. I
intend to be a part of the MariaDB Developer Community and would love to
start my journey through the Google Summer of Code this summer.
Do you expect any task that I should complete before submitting proposal for this particular project so that I can get a positive response.
Why this project was not allocated last year, even though it is being considered for Gsoc from last 3 years.

Amol Holani added a comment - 2017-03-12 07:04 Hi Kristian, I'm a senior year undergraduate student majoring in Computer Science. I intend to be a part of the MariaDB Developer Community and would love to start my journey through the Google Summer of Code this summer. Do you expect any task that I should complete before submitting proposal for this particular project so that I can get a positive response. Why this project was not allocated last year, even though it is being considered for Gsoc from last 3 years.

Mike Reiss added a comment - 2017-03-12 18:11

Hi,
I am Mike Reiss a MS Computer Science student and I would love to work on this project during GSoC 2017.I have studied the mysqlbinlog.cc file and experimented with the various options available in the my_options array of the tool. The proposed idea is straight forward to implement: We add the --start-gtid and --stop-gtid options to the array of options then parse the GTID passed to these options to get the GTID sequence number for the binlog. One quick question. Is there any relationship between a GTID sequence number and the argument passed to the --start-position option? that way we need to set the start position to the GTID sequence number. I am still doing more research into the source files and I will love to discuss this more with the mentor. I am having difficulties debugging mysqlbinlog on OS X sierra because it does not support GDB any ideas please?

Mike Reiss added a comment - 2017-03-12 18:11 Hi, I am Mike Reiss a MS Computer Science student and I would love to work on this project during GSoC 2017.I have studied the mysqlbinlog.cc file and experimented with the various options available in the my_options array of the tool. The proposed idea is straight forward to implement: We add the --start-gtid and --stop-gtid options to the array of options then parse the GTID passed to these options to get the GTID sequence number for the binlog. One quick question. Is there any relationship between a GTID sequence number and the argument passed to the --start-position option? that way we need to set the start position to the GTID sequence number. I am still doing more research into the source files and I will love to discuss this more with the mentor. I am having difficulties debugging mysqlbinlog on OS X sierra because it does not support GDB any ideas please?

Daniel Black added a comment - 2017-03-13 03:31

mikereiss - a number of gdb options for OS X Sierra are mentioned here http://stackoverflow.com/questions/39702871/gdb-kind-of-doesnt-work-on-macos-sierra . Its essential that you can work an debugger in your development environment and utilising a mentors time to achieve this isn't a productive use of their time especially if they use a different OS. There are plenty of other people/resources that should be able to help you with this.

Also related: https://lists.launchpad.net/maria-developers/msg09332.html and
https://lists.launchpad.net/maria-developers/msg08186.html

Daniel Black added a comment - 2017-03-13 03:31 mikereiss - a number of gdb options for OS X Sierra are mentioned here http://stackoverflow.com/questions/39702871/gdb-kind-of-doesnt-work-on-macos-sierra . Its essential that you can work an debugger in your development environment and utilising a mentors time to achieve this isn't a productive use of their time especially if they use a different OS. There are plenty of other people/resources that should be able to help you with this. Also related: https://lists.launchpad.net/maria-developers/msg09332.html and https://lists.launchpad.net/maria-developers/msg08186.html

Mike Reiss added a comment - 2017-03-13 13:04 - edited

@Daniel Black - I'm sorry I should have crafted my question as what is the recommended debugger used by MariaDB developers on OS X ? Thank you for the tip on gdb. Vicențiu on Maria-Developers recommended that I use lldb and it works great for me. Hope its fine with you I continue using lldb.

Mike Reiss added a comment - 2017-03-13 13:04 - edited @Daniel Black - I'm sorry I should have crafted my question as what is the recommended debugger used by MariaDB developers on OS X ? Thank you for the tip on gdb. Vicențiu on Maria-Developers recommended that I use lldb and it works great for me. Hope its fine with you I continue using lldb.

Sergei Golubchik made changes - 2018-01-08 10:07

Labels

gsoc14 gsoc15 gsoc16 gsoc17 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gtid mysqlbinlog replication

Rasmus Johansson (Inactive) made changes - 2019-02-25 14:48

Labels

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gtid mysqlbinlog replication

Sergei Golubchik made changes - 2019-03-04 17:56

Assignee

Andrei Elkin [ elkin ]

Richard Stracke made changes - 2019-07-05 13:45

Link

This issue relates to ~~MXS-2589~~ [ ~~MXS-2589~~ ]

Richard Stracke made changes - 2019-07-05 13:46

Link

This issue relates to ~~MXS-2581~~ [ ~~MXS-2581~~ ]

Geoff Montee (Inactive) made changes - 2019-07-22 19:07

Link

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

Geoff Montee (Inactive) added a comment - 2019-07-22 19:09

~~MDEV-20119~~ is somewhat related.

Geoff Montee (Inactive) added a comment - 2019-07-22 19:09 MDEV-20119 is somewhat related.

Geoff Montee (Inactive) made changes - 2019-07-22 19:12

Component/s		Replication [ 10100 ]
Component/s		Scripts & Clients [ 11002 ]

Geoff Montee (Inactive) made changes - 2019-07-22 19:13

Priority

Minor [ 4 ]

Major [ 3 ]

Andrei Elkin added a comment - 2019-08-15 12:22

{--start.stop}-position may be reused to accept the new type of GTID format string.

Andrei Elkin added a comment - 2019-08-15 12:22 { --start.stop}-position may be reused to accept the new type of GTID format string.

Julien Fritsch made changes - 2019-10-28 10:39

Assignee

Andrei Elkin [ elkin ]

Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]

Ralf Gebhardt made changes - 2019-12-02 10:39

Assignee

Ralf Gebhardt [ ralf.gebhardt@mariadb.com ]

Andrei Elkin [ elkin ]

Vicențiu Ciorbaru made changes - 2020-02-04 14:41

Labels

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gsoc20 gtid mysqlbinlog replication

Robert Bindar made changes - 2021-02-18 18:23

Labels

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gsoc20 gtid mysqlbinlog replication

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gsoc20 gsoc21 gtid mysqlbinlog replication

Ian Gilfillan made changes - 2021-04-13 23:50

Link

This issue relates to MDEV-25348 [ MDEV-25348 ]

Chris Calender (Inactive) made changes - 2021-04-14 16:08

Priority

Major [ 3 ]

Critical [ 2 ]

Sergei Golubchik made changes - 2021-07-06 15:41

Fix Version/s

10.7 [ 24805 ]

Ralf Gebhardt made changes - 2021-07-21 17:55

Due Date

2021-09-14

Andrei Elkin made changes - 2021-08-03 14:16

Assignee

Andrei Elkin [ elkin ]

Brandon Nesterenko [ JIRAUSER48702 ]

Brandon Nesterenko made changes - 2021-08-06 14:59

Status

Open [ 1 ]

In Progress [ 3 ]

Brandon Nesterenko added a comment - 2021-08-24 03:16 - edited

This is ready for review.

Commit: ~~f7e582ff9c5ace871c9b98ea8465956c1e94fb96~~

Buildbot: bb-10.7-MDEV-4989

- Updated commit Aug 27 with some documentation, code formatting, and slight code changes to help with ~~MDEV-20119~~

Brandon Nesterenko added a comment - 2021-08-24 03:16 - edited This is ready for review. Commit: f7e582ff9c5ace871c9b98ea8465956c1e94fb96 Buildbot: bb-10.7-MDEV-4989 Updated commit Aug 27 with some documentation, code formatting, and slight code changes to help with MDEV-20119

Brandon Nesterenko made changes - 2021-08-24 03:16

Assignee	Brandon Nesterenko [ JIRAUSER48702 ]	Andrei Elkin [ elkin ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Brandon Nesterenko added a comment - 2021-09-10 02:03

I have pushed a new commit which addresses an initial round of reviews from Andrei:

Commit: 02f98a22d2caef7c2953fe02b7f7516cd08c9544
Buildbot: bb-10.7-MDEV-4989

Brandon Nesterenko added a comment - 2021-09-10 02:03 I have pushed a new commit which addresses an initial round of reviews from Andrei: Commit: 02f98a22d2caef7c2953fe02b7f7516cd08c9544 Buildbot: bb-10.7-MDEV-4989

Sergei Golubchik made changes - 2021-09-14 19:34

Priority

Critical [ 2 ]

Major [ 3 ]

Ralf Gebhardt made changes - 2021-09-16 07:34

Due Date

2021-09-14

Ralf Gebhardt made changes - 2021-10-07 09:34

Fix Version/s		10.8 [ 26121 ]
Fix Version/s	10.7 [ 24805 ]

Sergei Golubchik made changes - 2021-10-29 12:00

Priority

Major [ 3 ]

Critical [ 2 ]

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

Workflow

MariaDB v3 [ 65819 ]

MariaDB v4 [ 131756 ]

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

Status

In Review [ 10002 ]

In Testing [ 10301 ]

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

Assignee

Andrei Elkin [ elkin ]

Alice Sherepa [ alice ]

Sergei Golubchik made changes - 2022-01-21 13:29

Link

This issue is part of ~~MDEV-27373~~ [ ~~MDEV-27373~~ ]

Alice Sherepa made changes - 2022-01-25 12:37

Status

In Testing [ 10301 ]

Stalled [ 10000 ]

Alice Sherepa made changes - 2022-01-25 12:38

Assignee

Alice Sherepa [ alice ]

Andrei Elkin [ elkin ]

Alice Sherepa added a comment - 2022-01-25 12:38

it is ok to push it into 10.8

Alice Sherepa added a comment - 2022-01-25 12:38 it is ok to push it into 10.8

Sergei Golubchik made changes - 2022-01-31 09:56

Fix Version/s		10.8.1 [ 26815 ]
Fix Version/s	10.8 [ 26121 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2022-01-31 09:56

Assignee

Andrei Elkin [ elkin ]

Brandon Nesterenko [ JIRAUSER48702 ]

Elena Stepanova made changes - 2022-10-16 14:16

Link

This issue causes MDEV-29803 [ MDEV-29803 ]

Ralf Gebhardt made changes - 2023-03-21 10:55

Labels

gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gsoc20 gsoc21 gtid mysqlbinlog replication

Preview_10.8 gsoc14 gsoc15 gsoc16 gsoc17 gsoc18 gsoc19 gsoc20 gsoc21 gtid mysqlbinlog replication

Rob Schwyzer (Inactive) made changes - 2024-04-04 22:00

Remote Link

This issue links to "Page (MariaDB Confluence)" [ 36745 ]

Rob Schwyzer (Inactive) made changes - 2024-04-05 18:34

Remote Link

This issue links to "Page (MariaDB Confluence)" [ 36745 ]

Jira Automation (IT) made changes - 2024-07-04 12:35

Zendesk Related Tickets

125514 200444 175152 125268

MariaDB Server

Support for GTID in mysqlbinlog

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration