From a83ee9d5c525c9a51a28f9d5ba52c36b35b1f727 Mon Sep 17 00:00:00 2001 From: Tadgh Date: Mon, 15 Jan 2024 10:36:20 -0800 Subject: [PATCH] Fix typo --- .../fhir/changelog/7_0_0/5555-avoid-resource-lob-column.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5555-avoid-resource-lob-column.yaml b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5555-avoid-resource-lob-column.yaml index 8ae0b2fab63..39593e8f27d 100644 --- a/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5555-avoid-resource-lob-column.yaml +++ b/hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_0_0/5555-avoid-resource-lob-column.yaml @@ -4,7 +4,7 @@ issue: 5555 title: "Previously, resource body content went into one of 2 columns on the HFJ_RES_VER table: RES_TEXT if the size was above a configurable threshold, or RES_TEXT_VC if it was below that threshold. Performance testing has shown that the latter is always faster, and that on - Postgres the use of the latter is particularly problematic since it maps to the + Postgres the use of the former is particularly problematic since it maps to the largeobject table which isn't the recommended way of storing high frequency objects. The configurable threshold is now ignored, and the latter column is always used. Any legacy data in the former column will still be read however."