Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View


Categories: connectors experimental galera main
Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

connectors experimental galera main
f8e0029ee007...
f8e0029ee0076644f87867df66b9787ac79a9cde
Andrei Elkin
Partial all but 3 hunks revert has_/lock/unlock- temporary_tables hunks of temporary_tables.cc.
f3a5d38fa7bd...
f3a5d38fa7bd51cfff41892cc3c12fceab794964
Andrei Elkin
Revert "MDEV-37686 rpl.create_or_replace_mix2 fails in MDEV-35915 branch"

This reverts commit 3241798214b066d62ba3274ba5dc29549349ca65.
Due to MDEV-38212.
edabb01b2865...
edabb01b28653e0fe282c6f5b8fa6642c2fb59bd
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

fts_optimize_table() : Assigns thd to transaction even it is
called via user_thread or fulltext optimize thread.
e963f4155c38...
e963f4155c388c95e09d7f9c5c3ec1da4bb16a78
Alexander Barkov
MDEV-38249 Refactoring: Change Item_save_in_value() not to return SQL NULL

Fixing the return type of Type_handler::Item_save_in_value() from
bool to void.

Adding a new method st_value::is_null().

This makes the code less confusing.
e883e0f00fbc...
e883e0f00fbc9c61ee9644af82d5556d3db73d56
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Add FTSQueryExecutor class as a thin abstraction over QueryExecutor.
This class takes care of open, lock, read, insert, delete
for all auxiliary tables INDEX_[1..6], common FTS tables
(DELETED, DELETED_CACHE, BEING_DELETED, CONFIG..)

FTSQueryExecutor Class which has the following function:
Auxiliary table functions : insert_aux_record(), delete_aux_record(),
    read_aux(), read_aux_all()

FTS common table functions : insert_common_record(), delete_common_record(),
    delete_all_common_records(), read_all_common()

FTS CONFIG table functions : insert_config_record(), update_config_record(),
                            delete_config_record(), read_config_with_lock()
deb34bc4f02a...
deb34bc4f02a104ad73324380a883ca743312135
Marko Mäkelä
Cleanup: Merge recv_recovery_read_checkpoint() to srv_start()
d00e0f71a440...
d00e0f71a440cd22c995fcc38a0c07bc027c8383
Marko Mäkelä
MDEV-33817/MDEV-37170 fixup: Remove evex512

It turns out that there is no need to use the evex512 target attribute
that had been introduced in GCC 14 and clang 18, and will be
removed in GCC 16.

At the time when the evex512 attribute was introduced, Intel had plans
to release products with AVX10.1-256, supporting the AVX512 instruction set
but limited to 256-bit registers.  The evex512 attribute would have been
needed to "opt in" to the 512-bit instruction variants (using the EVEX
instruction prefix). Later on, Intel revised its plans to make AVX10.1
always 512-bit.

Reviewed by: Kristian Nielsen
c788836f4202...
c788836f42027825157609109177604d0cf5241a
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Refactor fetch, optimize to QueryExecutor and
standardize processor API. Replaced legacy SQL-graph
paths with QueryExecutor-based reads/writes:
fts_query code now uses QueryExecutor::read(), read_by_index()
with RecordCallback (updating fts_query_match_document(),
fts_query_is_in_proximity_range(), and fts_expand_query() to call
fts_query_fetch_document() instead of fts_doc_fetch_by_doc_id(),
which was removed along with FTS_FETCH_DOC_BY_DOC_ID_* macros);

Rewrote fts_optimize_write_word() to delete (or) insert via
FTSQueryExecutor::delete_aux_record()/insert_aux_record()
using fts_aux_data_t;
c6f61e8d184a...
c6f61e8d184a73f2b00784740891843954c1af3e
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce QueryExecutor to perform direct InnoDB record scans
with a callback interface and consistent-read handling.
Also handles basic DML operation on clustered index of the table

Newly Added file row0query.h & row0query.cc

QueryExecutor class the following apis
read(): iterate clustered index with RecordCallback
read_by_index(): scan secondary index and fetch clustered row
lookup_clustered_record(): resolve PK from secondary rec
process_record_with_mvcc(): build version via read view
and skip deletes
insert_record(): Insert tuple into table's clustered index
select_for_update(): Lock the record which matches with search_tuple
update_record():  Update the currently selected and X-locked
clustered record.
delete_record():  Delete the clustered record identified by tuple
delete_all(): Delete all clustered records in the table
replace_record(): Tries update via select_for_update() +
  update_record(); if not found, runs insert_record.
c6120692bd01...
c6120692bd01cacbc9121d8d1063369076ad8eb1
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce AuxCompareMode and AuxRecordReader to scan FTS auxiliary
indexes with compare+process callbacks.

Replace legacy SQL-graph APIs with typed executor-based ones:
-Add fts_index_fetch_nodes(trx, index, word, user_arg,
                          FTSRecordProcessor,compare_mode).
-Redefine fts_write_node() to use FTSQueryExecutor and fts_aux_data_t.

Implement write path via delete_aux_record (or) insert_aux_record.
Keep lock-wait retry handling and memory limit checks.

Change fts_select_index{,_by_range,_by_hash} return type
from ulint to uint8_t and simplify return flow.
Include fts0exec.h in fts0priv.h and update declarations accordingly.
bd2153e8453d...
bd2153e8453db9c30bc7836b07349249b1f471a1
Marko Mäkelä
WIP MDEV-37949: Implement innodb_log_archive, innodb_lsn_archived

TODO: Make innodb_log_archive=ON writes fully work!

TODO: Rename log files and set innodb_lsn_archived on checkpoint.

TODO: Implement recovery from archived log.

The new setting SET GLOBAL innodb_log_archive=ON will enable log
archiving as soon as the current ib_logfile0 is about to wrap around.

The read-only variable innodb_lsn_archived will reflect the LSN
since when a complete InnoDB log archive is available. If it is
0 at startup, it will be recovered from the log files. If
innodb_log_archive=OFF, this variable will be adjusted to the
latest checkpoint every time a log checkpoint is executed.
If innodb_log_archive=ON, the value should not change.

When innodb_log_archive=ON, the setting SET GLOBAL innodb_log_file_size
will affect subsequently created log files when the file that is being
currently written is running out.

log_t::archive_new_write(): Create and allocate a new log file,
and write the outstanding data to both the current and the new file.

log_t::archive_new_mmap(): Create and memory-map a new log file,
and update file_size to resize_target.

log_t::archive_set_size(): Ensure that resize_target is set for
new archived log files.

log_t::first_lsn: This should be the start of the current log file,
to be consulted in log_t::write_checkpoint() when renaming files.

log_write_buf(): Add the parameter max_length, the file wrap limit.

mtr_t::finish_writer(): Specialize for innodb_log_archive=ON

innodb_log_archive_update(): Assign log_sys.archived_lsn to the latest
checkpoint; it should be usable. If the log buffer is about to wrap
around, back off and retry.

log_t::archived_mmap_switch_prepare(): Create and memory-map a new log
file. TODO: Do we need a separate function from append_prepare_wait()?

log_t::append_prepare<log_t::ARCHIVED_MMAP>(): Special case.

log_t::archived_mmap_switch_complete(): Switch to the buffer that was
created in archived_mmap_switch_prepare().

mtr_t::finish_writer(): Invoke log_close() only if innodb_log_archive=OFF.
b9140102a3cd...
b9140102a3cde4a67a076cdf16b9b10c6dcc453a
ParadoxV5
could that be?
b87a42d36459...
b87a42d36459ff9c2b0ad35a9a3291c7a4cf9190
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce ConfigReader callback to extract key, value from
fulltext config common table (CONFIG). This table has
<key, value> schema.

Simplifield all function which uses CONFIG tale. These
functions uses executor.insert_config_record(), update_config_record()
instead of SQL or query graph.
af6dd561a18a...
af6dd561a18aac69c24386c0081b03b53f09ae7d
bsrikanth-mariadb
MDEV-36523: Load basic stats from trace into optimizer

This task loads the stats of the tables that are used in a query,
from the trace into the optimizer. This feature is also controlled
by optimizer_record_context, and is not enabled by default.
The stats such as num_of_records present in the table, indexes if present,
their names, along with the average number of records_per_key
with in each index are loaded from the trace.
Additionally, stats from range analysis i.e. ranges, and the
corresponding number of records are also loaded from the trace.

The trace context which is in JSON format is firstly set into the
session variable optimizer_trace_stored_context.
Later, when a user issues a query, the contents of this variable is
parsed and an in memory representation is built using the class
Optimizer_context_replay. This class is then used by the optimizer
to update and save original values of the tables, indexes, and range stats
in the methods "set_statistics_for_table()" of sql_statistics.cc, and
"check_quick_select()" of opt_range.cc.
After the query gets finished, the statistics that were updated
in the optimizer are restored back to the saved original values.

The entry point for parsing the json structure is in
"mysql_execute_command()" of sql_parse.cc, and similarly exit point
i.e. to restore the saved stats of the optimizer is at the end
of the same method.

Two new warning/error messages are introduced:
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_PARSE_FAILED, and
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_MATCH_FAILED
aea6a8c8caa9...
aea6a8c8caa9f74c42c0998b872e1eb016090704
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Refactor fetch, optimize to QueryExecutor and
standardize processor API. Replaced legacy SQL-graph
paths with QueryExecutor-based reads/writes:
fts_query code now uses QueryExecutor::read(), read_by_index()
with RecordCallback (updating fts_query_match_document(),
fts_query_is_in_proximity_range(), and fts_expand_query() to call
fts_query_fetch_document() instead of fts_doc_fetch_by_doc_id(),
which was removed along with FTS_FETCH_DOC_BY_DOC_ID_* macros);

Rewrote fts_optimize_write_word() to delete (or) insert via
FTSQueryExecutor::delete_aux_record()/insert_aux_record()
using fts_aux_data_t;
ad44e1b964f7...
ad44e1b964f75f7cb0b78fa27d84ab2fe2931697
mariadb-satishkumar
MDEV-36993: Format log for srv_mon_reset_all
a2c2f3f3269b...
a2c2f3f3269b21fe2842bf22fc4b1880edced775
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

- Removed fts0sql.cc file.
- Removed commented fts funtions
- Removed fts_table_t from fts_query_t and fts_optimize_t
a1da6555fb4d...
a1da6555fb4dc486ff463f8337eb497bd8820a1e
Aleksey Midenkov
MDEV-16686 DDL in procedure propagates no locking to tables locked by DML

TABLE_LIST parsed from procedure code is transferred into tables to
lock for INSERT. The procedure code is CREATE VIEW so its TABLE_LIST
is parsed as TL_IGNORE, but same view exists and when existing view is
opened mysql_make_view() uses same TABLE_LIST that was initialized
from CREATE VIEW and then added as part of prelocking context. So
existing view is opened and its table is assigned TL_IGNORE from
prelocking context. Finally, INSERT has TABLE_LIST duplication: the
one that was parsed from INSERT; the another one came from procedure
prelocking, its lock_type came from the procedure code and the real
table was found via existing view.

The sequence of execution:

1. Procedure p is compiled as part of open_and_process_routine(), its
  code is parsed and create_or_alter_view_finalize() initializes v
  TABLE_LIST as TL_IGNORE;
2. Procedure p prelocking adds v to prelocking_ctx with TL_IGNORE;
3. DML prelocking adds v from prelocking_ctx;
4. View is opened, mysql_make_view() assigns t lock_type from v;
5. open_and_lock_tables() attempts to lock t with TL_IGNORE.

The fix skips TL_IGNORE at 2. when table list parsed by procedure is
added for prelocking:

        if (my_hash_insert(&m_sptabs, (uchar *)tab))
          return FALSE;

m_sptabs designation was defined as strictly for prelocking:

  /**
    Multi-set representing optimized list of tables to be locked by this
    routine. Does not include tables which are used by invoked routines.

    @note
    For prelocking-free SPs this multiset is constructed too.
    We do so because the same instance of sp_head may be called both
    in prelocked mode and in non-prelocked mode.
  */
  HASH m_sptabs;

The fix was proposed by Sergei Golubchik <[email protected]>.
9bc93a13b2ae...
9bc93a13b2ae6218c57afa45e63886bee746bf75
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce ConfigReader callback to extract key, value from
fulltext config common table (CONFIG). This table has
<key, value> schema.

Simplifield all function which uses CONFIG tale. These
functions uses executor.insert_config_record(), update_config_record()
instead of SQL or query graph.
99c9d1dc8645...
99c9d1dc8645ec6af5a14351f4917f33f28df091
Rex Johnston
MDEV-38236 Produce parseable output from unit::print for use in fixing query plans

Quick demo hacked together as an example.
Have not altered parser to understand what a 'semi join' is, but
explain format=sql select ...
is working.
93164861a0ad...
93164861a0ad1e858edb6ab28efb8f2e8f696fef
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce QueryExecutor to perform direct InnoDB record scans
with a callback interface and consistent-read handling.
Also handles basic DML operation on clustered index of the table

Newly Added file row0query.h & row0query.cc

QueryExecutor class the following apis
read(): iterate clustered index with RecordCallback
read_by_index(): scan secondary index and fetch clustered row
lookup_clustered_record(): resolve PK from secondary rec
process_record_with_mvcc(): build version via read view
and skip deletes
insert_record(): Insert tuple into table's clustered index
select_for_update(): Lock the record which matches with search_tuple
update_record():  Update the currently selected and X-locked
clustered record.
delete_record():  Delete the clustered record identified by tuple
delete_all(): Delete all clustered records in the table
replace_record(): Tries update via select_for_update() +
  update_record(); if not found, runs insert_record.
88042250e122...
88042250e122a3334ed227ebf9469efd65cd412b
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Add FTSQueryExecutor class as a thin abstraction over QueryExecutor.
This class takes care of open, lock, read, insert, delete
for all auxiliary tables INDEX_[1..6], common FTS tables
(DELETED, DELETED_CACHE, BEING_DELETED, CONFIG..)

FTSQueryExecutor Class which has the following function:
Auxiliary table functions : insert_aux_record(), delete_aux_record(),
    read_aux(), read_aux_all()

FTS common table functions : insert_common_record(), delete_common_record(),
    delete_all_common_records(), read_all_common()

FTS CONFIG table functions : insert_config_record(), update_config_record(),
                            delete_config_record(), read_config_with_lock()
7a34b7e56836...
7a34b7e56836ff2c759f813878ec93583d35b54c
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

- Removed fts0sql.cc file.
- Removed commented fts funtions
- Removed fts_table_t from fts_query_t and fts_optimize_t
69ec1d6cfa56...
69ec1d6cfa564290dbdddd368944e77cbd1d5f0b
Marko Mäkelä
Merge 10.6 into 10.11
60e0b2abb964...
60e0b2abb964344af651e7377f60592e5a2c3c74
bsrikanth-mariadb
MDEV-36523: Load basic stats from trace into optimizer

This task loads the stats of the tables that are used in a query,
from the trace into the optimizer. This feature is also controlled
by optimizer_record_context, and is not enabled by default.
The stats such as num_of_records present in the table, indexes if present,
their names, along with the average number of records_per_key
with in each index are loaded from the trace.
Additionally, stats from range analysis i.e. ranges, and the
corresponding number of records are also loaded from the trace.

The trace context which is in JSON format is firstly set into the
session variable optimizer_trace_stored_context.
Later, when a user issues a query, the contents of this variable is
parsed and an in memory representation is built using the class
Optimizer_context_replay. This class is then used by the optimizer
to update and save original values of the tables, indexes, and range stats
in the methods "set_statistics_for_table()" of sql_statistics.cc, and
"check_quick_select()" of opt_range.cc.
After the query gets finished, the statistics that were updated
in the optimizer are restored back to the saved original values.

The entry point for parsing the json structure is in
"mysql_execute_command()" of sql_parse.cc, and similarly exit point
i.e. to restore the saved stats of the optimizer is at the end
of the same method.

Two new warning/error messages are introduced:
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_PARSE_FAILED, and
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_MATCH_FAILED
58bb24ad9b5a...
58bb24ad9b5ab090b6aa8e7c15f43258d0fc8705
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce AuxCompareMode and AuxRecordReader to scan FTS auxiliary
indexes with compare+process callbacks.

Replace legacy SQL-graph APIs with typed executor-based ones:
-Add fts_index_fetch_nodes(trx, index, word, user_arg,
                          FTSRecordProcessor,compare_mode).
-Redefine fts_write_node() to use FTSQueryExecutor and fts_aux_data_t.

Implement write path via delete_aux_record (or) insert_aux_record.
Keep lock-wait retry handling and memory limit checks.

Change fts_select_index{,_by_range,_by_hash} return type
from ulint to uint8_t and simplify return flow.
Include fts0exec.h in fts0priv.h and update declarations accordingly.
546d15455a19...
546d15455a196186e19be8d63804fabca5e33946
ParadoxV5
this is a temp change for debugging WinDoze
53f237a36ceb...
53f237a36ceb3b207a4ca71b87514096026088b8
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

fts_optimize_table() : Assigns thd to transaction even it is
called via user_thread or fulltext optimize thread.
43346acdd4e6...
43346acdd4e62e3f540608d297ac0c12c3500c37
ParadoxV5
WinDoze is cursed.
429db8061fbb...
429db8061fbb82ba9acb819aa3525021b2bd8c02
bsrikanth-mariadb
MDEV-36523: Load basic stats from trace into optimizer

This task loads the stats of the tables that are used in a query,
from the trace into the optimizer. This feature is also controlled
by optimizer_record_context, and is not enabled by default.
The stats such as num_of_records present in the table, indexes if present,
their names, along with the average number of records_per_key
with in each index are loaded from the trace.
Additionally, stats from range analysis i.e. ranges, and the
corresponding number of records are also loaded from the trace.

The trace context which is in JSON format is firstly set into the
session variable optimizer_trace_stored_context.
Later, when a user issues a query, the contents of this variable is
parsed and an in memory representation is built using the class
Optimizer_context_replay. This class is then used by the optimizer
to update and save original values of the tables, indexes, and range stats
in the methods "set_statistics_for_table()" of sql_statistics.cc, and
"check_quick_select()" of opt_range.cc.
After the query gets finished, the statistics that were updated
in the optimizer are restored back to the saved original values.

The entry point for parsing the json structure is in
"mysql_execute_command()" of sql_parse.cc, and similarly exit point
i.e. to restore the saved stats of the optimizer is at the end
of the same method.

Two new warning/error messages are introduced:
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_PARSE_FAILED, and
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_MATCH_FAILED
3df8913f57d8...
3df8913f57d89d52b0270801404be4cf5945ec4b
Yuchen Pei
MDEV-9826 Use proper XXH streaming functions
37be5b9445eb...
37be5b9445eb1e8991b3b5329b049d8c77544941
ParadoxV5
how about this?
35c3f91a1290...
35c3f91a1290ac312cfc8dc769ebb9ce78617aeb
bsrikanth-mariadb
MDEV-36523: Load basic stats from trace into optimizer

This task loads the stats of the tables that are used in a query,
from the trace into the optimizer. This feature is controlled
by optimizer_replay_context, and points to an user defined variable name,
that has the context information.
The stats such as num_of_records present in the table, indexes if present,
their names, along with the average number of records_per_key
with in each index, cost of reading an index are loaded from the trace.
Additionally, stats from range analysis i.e. ranges, and the
corresponding number of records, along with their costs are also
loaded from the trace.

The trace context which is in JSON format is firstly set into the
user defined session variable, and this variable name is set to
optimizer_replay_context system variable.
Later, when a user issues a query, the contents of the json context is
parsed and an in memory representation is built using the class
Optimizer_context_replay. This class is then used by the optimizer
to update and save original values of the tables, indexes, and range stats
in the methods "set_statistics_for_table()" of sql_statistics.cc, and
"check_quick_select()" of opt_range.cc.
After the query gets finished, the statistics that were updated
in the optimizer are restored back to the saved original values.

The entry point for parsing the json structure is in
"mysql_execute_command()" of sql_parse.cc, and similarly exit point
i.e. to restore the saved stats of the optimizer is at the end
of the same method.

Two new warning/error messages are introduced:
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_PARSE_FAILED, and
ER_JSON_OPTIMIZER_REPLAY_CONTEXT_MATCH_FAILED
32d85c89a453...
32d85c89a45315e3bb4f055c84280a57d391ccd4
Yuchen Pei
MDEV-9826 Add one-shot hash functions to my_hasher_st for use in binary hash_sort

Rename my_hasher_st::hash to my_hasher_st::m_hash_byte for byte
streaming. Add my_hasher_st::m_hash_str for one-shot hashing.

Automatically convert one-shot to byte-streaming by restricting the
former on a string of length one, as before.

But now use one-shot functions whenever possible, i.e. in
my_hash_sort_*bin functions that apply the byte-streaming function on
a contiguous memory interval without transformation.

Only xxh is affected as BASE31 and CRC32C are homomorphic. The diff in
xxh results shows a slightly more even distribution.
21ae271d58cd...
21ae271d58cdb86af8122183807347e88e4c2df7
Alessandro Vetere
fixup MDEV-19123 Change default charset from latin1 to utf8mb4

Adjust the 128 indexes build test result.

Reviewed by: Alexander Barkov
1afc68293229...
1afc68293229286132fcb1126911e3157651b938
Marko Mäkelä
MDEV-36024 preparation: Shrink mtr_buf_t

mtr_t::get_log_size(): Remove.

mtr_t::crc32c(): New function: compute CRC-32C and determine the size,
including the sequence byte and the CRC-32C.

mtr_t::encrypt(): Return the size, similar to crc32c().

mtr_t::log_file_op(): Return the size written.

fil_name_write(): Remove. Let us invoke mtr_t::log_file_op() directly.

fil_names_clear(): Keep track of the available size without
invoking mtr_t::get_log_size().

mtr_buf_t::m_size: Remove.

mtr_buf_t::list_t: Use ilist instead of sized_ilist.

mtr_buf_t::for_each_block(): Remove. Let us allow iteration via
begin() and end(), without any lambda function objects.
18352dee253c...
18352dee253c7f93625e085fd33dd87756a3bab4
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce CommonTableReader callback to collect doc_id_t from
fulltext common tables (DELETED, BEING_DELETED, DELETED_CACHE,
BEING_DELETED_CACHE). These table share the same schema strucutre.

Simplified all function which uses DELETED, BEING_DELETED,
DELETED_CACHE, BEING_DELETED_CACHE table. These functions
uses executor.insert_common_record(), delete_common_record(),
delete_all_common_records() instead of SQL or query graph.

fts_table_fetch_doc_ids(): Changed the signature of the function
to pass the table name instead of fts_table_t.
11cda86eacb6...
11cda86eacb65a4a63e216dae97b463b9eb0c0ab
Marko Mäkelä
MDEV-37949: Introduce innodb_log_recovery_start, innodb_log_recovery_target

innodb_log_recovery_start: The checkpoint LSN to start recovery from.
This will be useful when recovering from an archived log.

innodb_log_recovery_target: The requested LSN to end recovery at.
This will be useful when recovering data files that were copied
as of a time that is before end of the available log.
0cbf3c102f50...
0cbf3c102f50f2c4253d41c7d062ee6edd288292
Thirunarayanan Balathandayuthapani
MDEV-28730 Remove internal parser usage from InnoDB fts

Introduce CommonTableReader callback to collect doc_id_t from
fulltext common tables (DELETED, BEING_DELETED, DELETED_CACHE,
BEING_DELETED_CACHE). These table share the same schema strucutre.

Simplified all function which uses DELETED, BEING_DELETED,
DELETED_CACHE, BEING_DELETED_CACHE table. These functions
uses executor.insert_common_record(), delete_common_record(),
delete_all_common_records() instead of SQL or query graph.

fts_table_fetch_doc_ids(): Changed the signature of the function
to pass the table name instead of fts_table_t.
BuildBot (0.8.9) working for the MariaDB project.
Page built: Thu 04 Dec 2025 17:55:33 (UTC)