From a01c8da2bd5d6ccc235fb545784348c64b718291 Mon Sep 17 00:00:00 2001 From: vramik Date: Thu, 23 Jan 2025 11:11:35 +0100 Subject: [PATCH] Update `index-creation-threshold` in migrate_db.adoc Closes #36669 Signed-off-by: vramik --- docs/documentation/upgrading/topics/migrate_db.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/documentation/upgrading/topics/migrate_db.adoc b/docs/documentation/upgrading/topics/migrate_db.adoc index 4e65d2e6cb4..87008be7112 100644 --- a/docs/documentation/upgrading/topics/migrate_db.adoc +++ b/docs/documentation/upgrading/topics/migrate_db.adoc @@ -11,11 +11,11 @@ To perform an automatic migration, start the server connected to the desired dat For example, creating an index on tables with millions of records can be time-consuming and cause a major service disruption. Therefore, a threshold of `300000` records exists for automatic migration. If the number of records exceeds this threshold, the index is not created. Instead, you find a warning in the server logs with the SQL commands that you can apply manually. -To change the threshold, set the `index-creation-threshold` property, value for the default `connections-liquibase` provider: +To change the threshold, set the `index-creation-threshold` property, value for the `connections-liquibase` provider: [source,bash] ---- -kc.[sh|bat] start --spi-connections-liquibase-default-index-creation-threshold=300000 +kc.[sh|bat] start --spi-connections-liquibase-quarkus-index-creation-threshold=300000 ---- === Manual relational database migration