Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, select query does not return the expected results.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: suresh(dot)thelkar(at)altair(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15755: After upgrading to 9.6.12 using pg_upgrade, select query does not return the expected results.
Date: 2019-04-15 16:15:13
Message-ID: 16625.1555344913@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> When we upgraded Postgres from 9.3.12 to 9.6.12 we observed that queries
> like the following are no longer giving the expected results.
> select * from xyz.job_attr where jobid = 'foo';
> [ but reindexing fixed it ]

What collation locale do you use in that database? (psql \l's
"Collate" column would say.) If it's not "C", the most likely
explanation is that you also upgraded the underlying OS, and glibc's
sort order for that locale changed from what it was before. If so,
reindexing is the appropriate cure. There isn't a lot we can do about
this inside Postgres, because we have no visibility into whether a
locale's behavior is different today than it was yesterday :-(

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-04-15 18:30:45 BUG #15757: Problem with the sequences node
Previous Message Tomas Vondra 2019-04-15 14:05:41 Re: BUG #15754: The CentOS RPM for PostgreSQL 11 disappeared and now throws a 404 error