From bfc5a6a291f1892647a1b78942e72d83b96fa1de Mon Sep 17 00:00:00 2001 From: Ewoud Kohl van Wijngaarden Date: Thu, 19 Dec 2024 14:11:39 +0100 Subject: [PATCH] Drop obsolete reference to checkpoint_segments In b7fda4a7c3478390941c191faaf64c7274d8b59c a note was dropped, but not entirely. Fixes: b7fda4a7c347 ("Add feedback from Github") --- guides/common/modules/con_postgresql-tuning.adoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/guides/common/modules/con_postgresql-tuning.adoc b/guides/common/modules/con_postgresql-tuning.adoc index a947fdc518..c17b55a668 100644 --- a/guides/common/modules/con_postgresql-tuning.adoc +++ b/guides/common/modules/con_postgresql-tuning.adoc @@ -41,7 +41,3 @@ Setting this value to 8 MB should be more than enough for most of the intensive * `autovacuum_vacuum_cost_limit`: The key defines the cost limit value for the vacuuming operation inside the autovacuum process to clean up the dead tuples inside the database relations. The cost limit defines the number of tuples that can be processed in a single run by the process. {Team} recommends setting the value to `2000` as it is for the _medium_, _large_, _extra-large_, and _extra-extra-large_ profiles, based on the general load that {Project} pushes on the PostgreSQL server process. - -ifndef::orcharhino[] -For more information, see https://bugzilla.redhat.com/show_bug.cgi?id=1867311#c12[BZ1867311: Upgrade fails when checkpoint_segments postgres parameter configured]. -endif::[]