From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: "Saraswat, Dhruv" <dhruv.saraswat@thermofisher.com>,
        "pgsql-sql@lists.postgresql.org" <pgsql-sql@lists.postgresql.org>,
        "Perumalla, Vijaya S." <Vijaya.Perumalla@thermofisher.com>,
        "AR,
    KarthikRaja" <karthikraja.ar@thermofisher.com>,
        "bhorhari,
    vikas" <vikas.bhorhari@thermofisher.com>,
        "SV,
    Sushanth" <sushanth.sv@thermofisher.com>,
        "Dahiya,
    Rohit" <rohit.dahiya@thermofisher.com>,
        "Thota,
    DurgaKumari" <Durga.Kumari@thermofisher.com>,
        "Venkatachalam,
    Sundarrajan" <Sundarrajan.Venkatachalam@thermofisher.com>,
        "Appandarajan, Vinoth" <vinoth.a@thermofisher.com>,
        "Barchhiha,
    Vaibhav" <vaibhav.barchhiha@thermofisher.com>,
        "Prajapati,
    Priya" <priya.prajapati@thermofisher.com>,
        "Kumar,
    Ravi" <ravi.kumar@thermofisher.com>,
        "Sarkar,
    Madhurima" <madhurima.sarkar@thermofisher.com>
Subject: Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5
 Version
In-reply-to: 
 <CAKFQuwb_dLFQ_K6n8RjjV32DmBkad7+RUqLBC1W9ZyHCNHYkAA@mail.gmail.com>
References: <EC08722A-A2DA-4D15-A41F-8BF80C7E656B@thermofisher.com>
 <CAKFQuwb_dLFQ_K6n8RjjV32DmBkad7+RUqLBC1W9ZyHCNHYkAA@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Thu, 08 Jul 2021 09:10:24 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1975903.1625762985.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 08 Jul 2021 12:49:45 -0400
Message-ID: <1975904.1625762985@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1975904.1625762985%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Thu, Jul 8, 2021 at 2:26 AM Saraswat, Dhruv <
> dhruv.saraswat@thermofisher.com> wrote:
>> We have a table in which 1 of the columns is called =E2=80=98name=E2=80=
=99 with a datatype
>> of =E2=80=98name=E2=80=99. This column stores username values, for exam=
ple =3D=3D>
>> dhruv.saraswat@thermofisher.com

> I unfortunately don't know the answer to your primary query but you are
> definitely misusing the "name" datatype.

Indeed.  I suspect that this was done as some sort of substitute for
declaring the column with collation "C", and the reason it's acting
differently in v12 is related to the fact that name columns are no
longer forced to behave as though they have collation "C".  We don't
have enough details to be sure of that though.

			regards, tom lane