| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| | |
bb-sachin-10.0-galera-merge
|
| |
| |
| |
| |
| |
| |
| | |
Currently galera has capability of using delta transfer algorithm (rsync)
for SST. But for using delta transfer we have change/copy wsrep_sst_rsync
wsrep_sst_rsync_wan. This patch creates a symbolic link of
wsrep_sst_rsync_wan to wsrep_sst_rsync.
|
| | |
|
| | |
|
| |\ |
|
| |\ \
| | | |
| | | | |
MDEV-12646: wsrep.cnf - wsrep_on=1 by default
|
| |/ /
| | |
| | |
| | | |
From: https://github.com/devexp-db/mariadb/blob/f27/mariadb-galera.cnf.patch
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
In some slave like p8-xenial-bintar-debug we are using C90 standard
which does not allow declaration and code to be mixed.
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix Galera crash at startup when compiled with gcc 6
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge pull request https://github.com/MariaDB/server/pull/343
contributed by Eric Herman.
|
| | | |
| | | |
| | | |
| | | | |
clarify the license
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Tasks:-
Changes in wsrep_dirty_reads variable
1.) Global + Session scope (Current: session-only)
2.) Can be set using command line.
3.) Allow all commands that do not change data (besides SELECT)
4.) Allow prepared Statements that do not change data
5.) Works with wsrep_sync_wait enabled
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 72fd15f7c31aa3e3705ae1b005a3247a985c5bb3.
# Conflicts:
# mysql-test/suite/galera/r/galera_var_dirty_reads.result
# mysql-test/suite/galera/t/galera_var_dirty_reads.test
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Problem:-
The condition that checks for node readiness is too strict as it does
not allow SELECTs even if these selects do not access any tables.
For example,if we run
SELECT 1;
OR
SELECT @@max_allowed_packet;
Solution:-
We need not to report this error when all_tables(lex->query_tables)
is NULL:
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In Galera case this assertion is too strict as conflicting lock
could be same as lock here.
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Problem:-
This crash happens because logged stmt is quite big and while writing
Annotate_rows_log_event it throws EFBIG error but we ignore this error
and do not call cache_data->set_incident().
Solution:-
When we normally write Binlog_log_event we check for error EFBIG, but we did
do this for Annotate_rows_log_event. We check for this error and call
cache_data->set_incident() accordingly.
# Conflicts:
# sql/log.cc
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
This is another correction of the patch for bug mdev-12670.
If a derived table is merged into a select with STRAIGHT_JOIN
modifier all IN subquery predicates contained in the
specification of the derived table cannot be subject to
conversion to semi-joins.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
This patch is a correction of the patch for bug mdev-12670.
With the current code handling semi-joins the following must
be taken into account.
Conversion of an IN subquery predicate into semi-join
has to be blocked if the predicate occurs:
(a) in the ON expression of an outer join
(b) in the ON expression of an inner join embedded directly
or indirectly in the inner nest of an outer join.
The patch for mdev-12670 blocked conversion to semi-joins only
in the case (a), but not in the case (b). This patch blocks
the conversion in both cases.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
-DCMAKE_BUILD_TYPE=Debug
fix incorrect merge, 831b531895 was not fully merged into 10.0
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
uploaded 10.0, analyzed everything with the Impact=High
(and a couple of Medium)
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In a merge conflict resolution, callers of the added function
rec_field_len_in_chars() were removed, but the function itself was not.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|