From 6c9b7ad4083bb36e8d62315d563b9c14a5963897 Mon Sep 17 00:00:00 2001 From: Mahendrakar Srinivasarao Date: Tue, 10 Nov 2026 14:05:25 +0000 Subject: [PATCH v4 3/3] Fix long description of extension_control_path The long description of extension_control_path says that the remaining extension script and secondary control files are loaded from the same directory where the primary control file was found. That is not the case if the primary control file specifies a "directory". Adjust it to match the documentation of extension_control_path. Since this changes a translatable string, apply to master only. --- src/backend/utils/misc/guc_parameters.dat | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/utils/misc/guc_parameters.dat b/src/backend/utils/misc/guc_parameters.dat index 75d832eb570..93d1399d518 100644 --- a/src/backend/utils/misc/guc_parameters.dat +++ b/src/backend/utils/misc/guc_parameters.dat @@ -1069,7 +1069,7 @@ { name => 'extension_control_path', type => 'string', context => 'PGC_SUSET', group => 'CLIENT_CONN_OTHER', short_desc => 'Sets the path for extension control files.', - long_desc => 'The remaining extension script and secondary control files are then loaded from the same directory where the primary control file was found.', + long_desc => 'The remaining extension script and secondary control files are then loaded from the same directory where the primary control file was found, unless the primary control file specifies a different directory.', flags => 'GUC_SUPERUSER_ONLY', variable => 'Extension_control_path', boot_val => '"$system"', -- 2.43.0