move settings to H3 level

docs/en/engines/database-engines/index.md

@@ -20,6 +20,8 @@ Here is a complete list of available database engines. Follow the links for more
 
 -   [PostgreSQL](../../engines/database-engines/postgresql.md)
 
+-   [MaterializedMySQL](../../engines/database-engines/materialized-postgresql.md)
+
 -   [Replicated](../../engines/database-engines/replicated.md)
 
 -   [SQLite](../../engines/database-engines/sqlite.md)

docs/en/engines/database-engines/materialized-mysql.md

@@ -26,14 +26,30 @@ ENGINE = MaterializedMySQL('host:port', ['database' | database], 'user', 'passwo
 -   `user` — MySQL user.
 -   `password` — User password.
 
-**Engine Settings**
+## Engine Settings
 
--   `max_rows_in_buffer` — Maximum number of rows that data is allowed to cache in memory (for single table and the cache data unable to query). When this number is exceeded, the data will be materialized. Default: `65 505`.
--   `max_bytes_in_buffer` —  Maximum number of bytes that data is allowed to cache in memory (for single table and the cache data unable to query). When this number is exceeded, the data will be materialized. Default: `1 048 576`.
--   `max_flush_data_time` — Maximum number of milliseconds that data is allowed to cache in memory (for database and the cache data unable to query). When this time is exceeded, the data will be materialized. Default: `1000`.
--   `max_wait_time_when_mysql_unavailable` — Retry interval when MySQL is not available (milliseconds). Negative value disables retry. Default: `1000`.
--   `allows_query_when_mysql_lost` — Allows to query a materialized table when MySQL is lost. Default: `0` (`false`).
--   `materialized_mysql_tables_list` — a comma-separated list of mysql database tables, which will be replicated by MaterializedMySQL database engine. Default value: empty list — means whole tables will be replicated.
+### max_rows_in_buffer
+
+`max_rows_in_buffer` — Maximum number of rows that data is allowed to cache in memory (for single table and the cache data unable to query). When this number is exceeded, the data will be materialized. Default: `65 505`.
+
+### max_bytes_in_buffer
+
+`max_bytes_in_buffer` —  Maximum number of bytes that data is allowed to cache in memory (for single table and the cache data unable to query). When this number is exceeded, the data will be materialized. Default: `1 048 576`.
+
+### max_flush_data_time
+
+`max_flush_data_time` — Maximum number of milliseconds that data is allowed to cache in memory (for database and the cache data unable to query). When this time is exceeded, the data will be materialized. Default: `1000`.
+
+### max_wait_time_when_mysql_unavailable
+
+`max_wait_time_when_mysql_unavailable` — Retry interval when MySQL is not available (milliseconds). Negative value disables retry. Default: `1000`.
+
+### allows_query_when_mysql_lost
+`allows_query_when_mysql_lost` — Allows to query a materialized table when MySQL is lost. Default: `0` (`false`).
+
+### materialized_mysql_tables_list
+
+`materialized_mysql_tables_list` — a comma-separated list of mysql database tables, which will be replicated by MaterializedMySQL database engine. Default value: empty list — means whole tables will be replicated.
 
 ```sql
 CREATE DATABASE mysql ENGINE = MaterializedMySQL('localhost:3306', 'db', 'user', '***')
@@ -42,12 +58,17 @@ CREATE DATABASE mysql ENGINE = MaterializedMySQL('localhost:3306', 'db', 'user',
         max_wait_time_when_mysql_unavailable=10000;
 ```
 
-**Settings on MySQL-server Side**
+## Settings on MySQL-server Side
 
 For the correct work of `MaterializedMySQL`, there are few mandatory `MySQL`-side configuration settings that must be set:
 
-- `default_authentication_plugin = mysql_native_password` since `MaterializedMySQL` can only authorize with this method.
-- `gtid_mode = on` since GTID based logging is a mandatory for providing correct `MaterializedMySQL` replication.
+### default_authentication_plugin 
+
+`default_authentication_plugin = mysql_native_password` since `MaterializedMySQL` can only authorize with this method.
+
+### gtid_mode
+
+`gtid_mode = on` since GTID based logging is a mandatory for providing correct `MaterializedMySQL` replication.
 
 :::note 
 While turning on `gtid_mode` you should also specify `enforce_gtid_consistency = on`.
@@ -57,8 +78,13 @@ While turning on `gtid_mode` you should also specify `enforce_gtid_consistency =
 
 When working with the `MaterializedMySQL` database engine, [ReplacingMergeTree](../../engines/table-engines/mergetree-family/replacingmergetree.md) tables are used with virtual `_sign` and `_version` columns.
 
-- `_version` — Transaction counter. Type [UInt64](../../sql-reference/data-types/int-uint.md).
-- `_sign` — Deletion mark. Type [Int8](../../sql-reference/data-types/int-uint.md). Possible values:
+### \_version
+
+`_version` — Transaction counter. Type [UInt64](../../sql-reference/data-types/int-uint.md).
+
+### \_sign
+
+`_sign` — Deletion mark. Type [Int8](../../sql-reference/data-types/int-uint.md). Possible values:
     - `1` — Row is not deleted,
     - `-1` — Row is deleted.
 

docs/en/engines/database-engines/materialized-postgresql.md

@@ -150,21 +150,21 @@ Replication of [**TOAST**](https://www.postgresql.org/docs/9.5/storage-toast.htm
 
 ## Settings {#settings}
 
-1. `materialized_postgresql_tables_list` {#materialized-postgresql-tables-list}
+### `materialized_postgresql_tables_list` {#materialized-postgresql-tables-list}
 
     Sets a comma-separated list of PostgreSQL database tables, which will be replicated via [MaterializedPostgreSQL](../../engines/database-engines/materialized-postgresql.md) database engine.
 
     Default value: empty list — means whole PostgreSQL database will be replicated.
 
-2. `materialized_postgresql_schema` {#materialized-postgresql-schema}
+### `materialized_postgresql_schema` {#materialized-postgresql-schema}
 
     Default value: empty string. (Default schema is used)
 
-3. `materialized_postgresql_schema_list` {#materialized-postgresql-schema-list}
+### `materialized_postgresql_schema_list` {#materialized-postgresql-schema-list}
 
     Default value: empty list. (Default schema is used)
 
-4. `materialized_postgresql_allow_automatic_update` {#materialized-postgresql-allow-automatic-update}
+### `materialized_postgresql_allow_automatic_update` {#materialized-postgresql-allow-automatic-update}
 
     Do not use this setting before 22.1 version.
 
@@ -177,7 +177,7 @@ Replication of [**TOAST**](https://www.postgresql.org/docs/9.5/storage-toast.htm
 
     Default value: `0`.
 
-5. `materialized_postgresql_max_block_size` {#materialized-postgresql-max-block-size}
+### `materialized_postgresql_max_block_size` {#materialized-postgresql-max-block-size}
 
     Sets the number of rows collected in memory before flushing data into PostgreSQL database table.
 
@@ -187,11 +187,11 @@ Replication of [**TOAST**](https://www.postgresql.org/docs/9.5/storage-toast.htm
 
     Default value: `65536`.
 
-6. `materialized_postgresql_replication_slot` {#materialized-postgresql-replication-slot}
+### `materialized_postgresql_replication_slot` {#materialized-postgresql-replication-slot}
 
     A user-created replication slot. Must be used together with `materialized_postgresql_snapshot`.
 
-7. `materialized_postgresql_snapshot` {#materialized-postgresql-snapshot}
+### `materialized_postgresql_snapshot` {#materialized-postgresql-snapshot}
 
     A text string identifying a snapshot, from which [initial dump of PostgreSQL tables](../../engines/database-engines/materialized-postgresql.md) will be performed. Must be used together with `materialized_postgresql_replication_slot`.