Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28487

sequences not respect value of binlog_row_image with select nextval(seq_gen)

Details

    Description

      Even with binlog_row_image = full, select nextval(seq_gen) write to binlog in binlog_row_image = minimal mode.

       
      START TRANSACTION
      /*!*/;
      # at 15406542
      # at 15406588
      #220504 18:00:23 server id 202  end_log_pos 15406588 CRC32 0xe4eb5cad 	Annotate_rows:
      #Q> select nextval(seq_gen)
      ### INSERT INTO `t1`.`seq_gen`
      ### SET
      ###   @1=3000 /* LONGINT meta=0 nullable=0 is_null=0 */
      ###   @8=0 /* LONGINT meta=0 nullable=0 is_null=0 */
      

      Attachments

        Issue Links

          Activity

            Hi Andrei! This is ready for review:

            PR-2184

            bnestere Brandon Nesterenko added a comment - Hi Andrei! This is ready for review: PR-2184
            Elkin Andrei Elkin added a comment -

            Notes are provided on GH.

            Elkin Andrei Elkin added a comment - Notes are provided on GH.

            Pushed into 10.3 as 02e85ae.

            No merge conflicts occurred when cherry-picking through 10.10.

            The new test, rpl.rpl_row_img_sequence, may fail intermittently on kvm-ports-freebsd130-amd64 due to MDEV-28986

            bnestere Brandon Nesterenko added a comment - Pushed into 10.3 as 02e85ae . No merge conflicts occurred when cherry-picking through 10.10. The new test, rpl.rpl_row_img_sequence, may fail intermittently on kvm-ports-freebsd130-amd64 due to MDEV-28986

            People

              bnestere Brandon Nesterenko
              Richard Richard Stracke
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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