Skip to content

Conversation

grooverdan
Copy link
Member

This adds a unlock(LOCK_log) for the unlikely(!is_open()) branch

This adds a unlock(LOCK_log) for the unlikely(!is_open()) branch
knielsen added a commit that referenced this pull request Apr 24, 2015
…-in-MYSQL_BIN_LOG_write_incident

MDEV-7977 MYSQL_BIN_LOG::write_incident failing to release LOCK_log
@knielsen knielsen merged commit 2d6c0a5 into MariaDB:5.5 Apr 24, 2015
@knielsen
Copy link
Member

Pulled, thanks Daniel!

@grooverdan grooverdan deleted the MDEV-7977-mutex-unlock_LOCK_log-in-MYSQL_BIN_LOG_write_incident branch April 24, 2015 13:20
ankitkumar031 pushed a commit to ankitkumar031/server that referenced this pull request Apr 16, 2017
Merge pull request MariaDB#38 from mozilla/master
vuvova pushed a commit that referenced this pull request Jun 22, 2017
* BEGIN_TS(), COMMIT_TS() SQL functions;
* VTQ instead of packed stores secs + usecs like my_timestamp_to_binary() does;
* versioned SELECT to IB is translated with COMMIT_TS();
* SQL fixes:
  - FOR_SYSTEM_TIME_UNSPECIFIED condition compares to TIMESTAMP_MAX_VALUE;
  - segfault fix #36: multiple execute of prepared stmt;
  - different tables to same stored procedure fix (#39)
* Fixes of previous parts: ON DUPLICATE KEY, other misc fixes.
dr-m pushed a commit that referenced this pull request Nov 10, 2017
* BEGIN_TS(), COMMIT_TS() SQL functions;
* VTQ instead of packed stores secs + usecs like my_timestamp_to_binary() does;
* versioned SELECT to IB is translated with COMMIT_TS();
* SQL fixes:
  - FOR_SYSTEM_TIME_UNSPECIFIED condition compares to TIMESTAMP_MAX_VALUE;
  - segfault fix #36: multiple execute of prepared stmt;
  - different tables to same stored procedure fix (#39)
* Fixes of previous parts: ON DUPLICATE KEY, other misc fixes.
@svoj svoj added this to the 5.5 milestone Apr 22, 2018
ottok added a commit to ottok/mariadb that referenced this pull request Mar 11, 2023
Update patch that reverts changes from 10.0.26 that caused regression on PowerPC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants