Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5 Version

agora inbox for pgsql-sql@postgresql.org  
help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Saraswat, Dhruv <dhruv.saraswat@thermofisher.com>
Cc: pgsql-sql@lists.postgresql.org <pgsql-sql@lists.postgresql.org>
Cc: Perumalla, Vijaya S. <Vijaya.Perumalla@thermofisher.com>
Cc: AR, KarthikRaja <karthikraja.ar@thermofisher.com>
Cc: bhorhari, vikas <vikas.bhorhari@thermofisher.com>
Cc: SV, Sushanth <sushanth.sv@thermofisher.com>
Cc: Dahiya, Rohit <rohit.dahiya@thermofisher.com>
Cc: Thota, DurgaKumari <Durga.Kumari@thermofisher.com>
Cc: Venkatachalam, Sundarrajan <Sundarrajan.Venkatachalam@thermofisher.com>
Cc: Appandarajan, Vinoth <vinoth.a@thermofisher.com>
Cc: Barchhiha, Vaibhav <vaibhav.barchhiha@thermofisher.com>
Cc: Prajapati, Priya <priya.prajapati@thermofisher.com>
Cc: Kumar, Ravi <ravi.kumar@thermofisher.com>
Cc: Sarkar, Madhurima <madhurima.sarkar@thermofisher.com>
Subject: Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5 Version
Date: Thu, 08 Jul 2021 12:49:45 -0400
Message-ID: <1975904.1625762985@sss.pgh.pa.us> (raw)
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>

"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 ‘name’ with a datatype
>> of ‘name’. This column stores username values, for example ==>
>> 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

view thread (3+ messages)

Message-ID: <1975904.1625762985@sss.pgh.pa.us>
Permalink:  ../1975904.1625762985@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1975904.1625762985@sss.pgh.pa.us

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, dhruv.saraswat@thermofisher.com, pgsql-sql@lists.postgresql.org, Vijaya.Perumalla@thermofisher.com, karthikraja.ar@thermofisher.com, vikas.bhorhari@thermofisher.com, sushanth.sv@thermofisher.com, rohit.dahiya@thermofisher.com, Durga.Kumari@thermofisher.com, Sundarrajan.Venkatachalam@thermofisher.com, vinoth.a@thermofisher.com, vaibhav.barchhiha@thermofisher.com, priya.prajapati@thermofisher.com, ravi.kumar@thermofisher.com, madhurima.sarkar@thermofisher.com
  Subject: Re: UPPER() Function Not Working as Expected in PostgreSQL 12.5 Version
  In-Reply-To: <1975904.1625762985@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox