| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Václav Steiner <steiner(dot)vaclav(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Different query result, maybe bad index |
| Date: | 2021-02-24 11:59:18 |
| Message-ID: | d92931a935e2f574eccd4640b6b60046f7c506f2.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2021-02-24 at 12:50 +0100, Václav Steiner wrote:
> We have three servers running postgres 9.6, master and two slaves feeded by streaming replication.
> On of those slaves we are getting different query results. The replica was recreated from scratch, but problem persists.
>
> If set enable_indexscan='off' and set enable_bitmapscan='off' we get correct result.
> It looks like problem with some index...?
>
> Can anybody saw such behaviour?
If the problem persist when you rebuild the standby, I suspect that the servers
are running different C libraries or C library versions, so that the collations
with the same name behave slightly differently.
That could lead to the observed behavior with indexes on string data types.
Make sure to use the same C library version on both systems.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-02-24 12:00:50 | Re: Different query result, maybe bad index |
| Previous Message | Václav Steiner | 2021-02-24 11:50:04 | Different query result, maybe bad index |