From: Tom Lane <tgl@sss.pgh.pa.us>
To: kokdemir@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16849: index and table data inconsistency
Date: Tue, 02 Feb 2021 10:51:23 -0500
Message-ID: <3716068.1612281083@sss.pgh.pa.us> (raw)
In-Reply-To: <16849-17287340f8774148@postgresql.org>
References: <16849-17287340f8774148@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> I have data in a varchar field like '092', '00000000169', '0000001' and so
> on. There is a btree index on this field. my searches are similar to below
> ones.
> select searched_field from searched_table where searched_field = '092';
> When I search data, it uses the given index and returns no value. But when I
> disable index scan, it does a sequential scan and return data.
> We have witnessed this case in one index in our production(11.7) and
> staging(12.2) environments on same index. Then we dropped the index and
> recreate it. The problem is solved. But, to me, index and data must be
> consistent.
Most likely you got bit by an operating-system locale change causing
a change in sort order and thereby making the index self-inconsistent.
See
https://wiki.postgresql.org/wiki/Locale_data_changes
There's work afoot to have Postgres automatically notice when the
OS changes underneath it, but that's not done yet.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, kokdemir@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16849: index and table data inconsistency
In-Reply-To: <3716068.1612281083@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox