MDEV-4989: Support for GTID in mysqlbinlogpreview-10.8-MDEV-4989-mysqlbinlog-gtid

New Feature:
===========
This commit extends the mariadb-binlog capabilities to allow events
to be filtered by GTID ranges. More specifically, the following
capabilities are addressed:
   1) GTIDs can be used to filter results on local binlog files
   2) GTIDs can be used to filter results from remote servers
   3) For a given GTID range, its start-position is exclusive and
      its stop-position is inclusive. This allows users to receive
      events strictly after those that they already have, and is
      useful in cases such as: 1) events were received out of order
      and should be re-sent, or 2) specifying the  gtid state of a
      slave to get events newer than their current state.
      domain id are reset to their former values. If a seq_no is 0
      for start-position, it means to include the entirety of the
      domain. If a seq_no is 0 for stop-position, it means to
      exclude all events from that domain.
   4) Implemented --gtid-strict-mode that ensures the GTID event
      stream in each domain is monotonically increasing
   5) Added new level of verbosity in mysqlbinlog -vvv to print
      additional diagnostic information about invalid GTID states

To facilitate these features, the --start-position and
--stop-position arguments have been extended to accept values
formatted as a list of GTID positions, e.g.
--start-position=0-1-0,1-2-55

A few additional notes:
 1) this commit squashes together the commits:
f4319661120e-78a9d49907ba

 2) Changed rpl.rpl_blackhole_row_annotate test because it has
out of order GTIDs in its binlog, so I added
--skip-gtid-strict-mode

 3) After all binlog events have been written, the session server
    id and domain id are reset to their values in the global state.

Reviewed By:
===========
Andrei Elkin: <andrei.elkin@mariadb.com>

0 files changed, 0 insertions, 0 deletions