postgres.git / summary / log / commit / refs

commit    c581c9a7ac2af2c75567013f25125bd294d49ff2
Author:   Peter Eisentraut <peter@eisentraut.org>
Date:     Tue Nov 25 05:26:49 2025 +0000

    Remove obsolete comment
    
    This comment should probably have been moved to pg_locale_libc.c in
    commit 66ac94cdc79 (2024), but upon closer examination it was already
    completely obsolete then.
    
    The first part of the comment has been obsolete since commit
    85feb77aa09 (2017), which required that the system provides the
    required wide-character functions.
    
    The second part has been obsolete since commit e9931bfb751 (2024),
    which eliminated code paths depending on the global LC_CTYPE setting.
    
    Discussion: https://www.postgresql.org/message-id/flat/170308e6-a7a3-4484-87b2-f960bb564afa%40eisentraut.org


 src/backend/utils/adt/formatting.c | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/src/backend/utils/adt/formatting.c b/src/backend/utils/adt/formatting.c
index 5f7b3114da7..5bfeda2ffde 100644
--- a/src/backend/utils/adt/formatting.c
+++ b/src/backend/utils/adt/formatting.c
@@ -1616,16 +1616,6 @@ str_numth(char *dest, const char *num, enum TH_Case type)
  *			upper/lower/initcap functions
  *****************************************************************************/
 
-/*
- * If the system provides the needed functions for wide-character manipulation
- * (which are all standardized by C99), then we implement upper/lower/initcap
- * using wide-character functions, if necessary.  Otherwise we use the
- * traditional <ctype.h> functions, which of course will not work as desired
- * in multibyte character sets.  Note that in either case we are effectively
- * assuming that the database character encoding matches the encoding implied
- * by LC_CTYPE.
- */
-
 /*
  * collation-aware, wide-character-aware lower function
  *


[parent: ed823da12891]