Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdtRT-0055ze-UK for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 14:23:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qdtRS-00AuwT-Pi for pgsql-general@arkaria.postgresql.org; Wed, 06 Sep 2023 14:23:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdtRS-00AuwG-CK for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 14:23:38 +0000 Received: from mout-u-204.mailbox.org ([2001:67c:2050:101:465::204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qdtRO-0034cx-NB for pgsql-general@lists.postgresql.org; Wed, 06 Sep 2023 14:23:36 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4Rgl3P1SWYz9snr; Wed, 6 Sep 2023 16:23:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1694010209; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=W5mWrw08rTOop1Nfx6xPEVrGYE6Lq/c7kqJnX/Q/9H8=; b=QxCcPbeUmLQ8KfFLTm8IqvQYz9Pl/Tx3NG5xBV3Ej8/mpbXyFMuVbqbfyFLbBVaNDlZZ+O mxUjgxn+AVMfAepuvk3lzCUexqWDIgTOJTWZDIG2ugNDl/DlUZtFXZ8pML8Cg8cmMRMAit TEW1GXK3o9wBKy6odSd6wQoXL2DZQeLMRYf+rMi1uD62y6nYvqhgE/74QITEZqC9l+kl5F iz+01Yh5fzGidVsKLYA+iRfiQ+jKTwyBFQ4vMDNJFeKee+D5XEZLsaZs7lholKNlb+1xpw PFOZ0VV/fkMb+lBobQaY7hL+gKTEPnoGpgOY8NrHODcDfvLg/rtRUyIhMOfX9A== Date: Wed, 6 Sep 2023 16:23:28 +0200 (CEST) From: Erik Wienhold To: Sai Teja , pgsql-general@lists.postgresql.org Message-ID: <60182986.61.1694010208406@office.mailbox.org> In-Reply-To: References: Subject: =?UTF-8?Q?Re:_postgreSQL_UPPER_Method_is_con?= =?UTF-8?Q?verting_the_character_"=C2=B5"_into_"M"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Priority: 3 Importance: Normal X-Rspamd-Queue-Id: 4Rgl3P1SWYz9snr List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 06/09/2023 15:42 CEST Sai Teja wrote: > I am using UPPER document name for converting the text from lower case in= to > upper case. > But here for the below example > Command:- select UPPER(test=C2=B5) > Input :- test=C2=B5 > Output:- TESTM > Expected output :- TEST=C2=B5 > > Here, that character is converting into M which should not be case > The postgreSQL is hosted in Linux Machine which is using Locale_ctype:- e= n_US_utf.8 Use can use collation C or ucs_basic if you want to uppercase ASCII only: =09postgres=3D# SELECT upper('test=C2=B5' COLLATE "C"); =09 upper =09------- =09 TEST=C2=B5 =09(1 row) -- Erik