diff options
author | Davi Arnaut <Davi.Arnaut@Sun.COM> | 2009-05-11 20:54:00 -0300 |
---|---|---|
committer | Davi Arnaut <Davi.Arnaut@Sun.COM> | 2009-05-11 20:54:00 -0300 |
commit | 49d006a5b067eb97a6ba3c0043a20de515a1ca43 (patch) | |
tree | 066d5741ba4e35eaebb3f9b5bd12537e35009532 /scripts | |
parent | 4c226da20302f5f2affcfe2ea2b36931b230ecfe (diff) | |
download | mariadb-git-49d006a5b067eb97a6ba3c0043a20de515a1ca43.tar.gz |
Bug#44664: valgrind warning for COMMIT_AND_CHAIN and ROLLBACK_AND_CHAIN
The problem is that the internal variable used to specify a
transaction with consistent read was being used outside the
processing context of a START TRANSACTION WITH CONSISTENT
SNAPSHOT statement. The practical consequence was that a
consistent snapshot specification could leak to unrelated
transactions on the same session.
The solution is to ensure a consistent snapshot clause is
only relied upon for the START TRANSACTION statement.
This is already fixed in a similar way on 6.0.
mysql-test/r/consistent_snapshot.result:
Add test case result for Bug#44664
mysql-test/t/consistent_snapshot.test:
Add test case for Bug#44664
sql/sql_parse.cc:
The WITH CONSISTENT SNAPSHOT clause is only valid for the
START TRANSACTION statement.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions