From c8e2d422fd556292ab751392bf76f713fe9e9fc1 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 14 Aug 2024 08:02:32 +0200 Subject: Remove TRACE_SORT macro The TRACE_SORT macro guarded the availability of the trace_sort GUC setting. But it has been enabled by default ever since it was introduced in PostgreSQL 8.1, and there have been no reports that someone wanted to disable it. So just remove the macro to simplify things. (For the avoidance of doubt: The trace_sort GUC is still there. This only removes the rarely-used macro guarding it.) Reviewed-by: Heikki Linnakangas Discussion: https://www.postgresql.org/message-id/flat/be5f7162-7c1d-44e3-9a78-74dcaa6529f2%40eisentraut.org --- doc/src/sgml/config.sgml | 3 --- 1 file changed, 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index a1a1d58a436..2937384b001 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -11711,9 +11711,6 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' If on, emit information about resource usage during sort operations. - This parameter is only available if the TRACE_SORT macro - was defined when PostgreSQL was compiled. - (However, TRACE_SORT is currently defined by default.) -- cgit v1.2.3