Hi,
On 2020-11-13 15:14:23 -0800, Ernesto Hernández-Novich wrote:
> We have a PG 9.6.19/9.6.20 streaming replication set using PGDG
> packages over Debian 9 and 10. We started experiencing an interesting
> issue yesterday. This is the layout; all arrows are stream replication
> built using `pg_basebackup` over replication slots.
>
> Master N0 (9.6.19 / Debian 9) -> Replica A (9.6.19 / Debian 9)
> | |
> | +-----------------> Replica B (9.6.20 / Debian 10)
> |
> v
> Replica N1 (9.6.20 / Debian 9) -> Replica C (9.6.20 / Debian 9)
> |
> +------------------> Replica D (9.6.20 / Debian 10)
>
> We have a query that is a simple `select * from table where pk = 'fixed
> value'`. It fetches a *single* row vía a PK Index Scan using `=` on a
> TEXT value, no implicit conversions. Said query used to work fine
> across the replication set.
>
> After updating from 9.6.19 to 9.6.20, we noticed the query was not
> working on D. It did NOT bring any rows. If the query is attempted
> using LIKE or ~ (with a left-anchored pattern), the correct row is
> fetched BUT using a Sequential Scan. We checked B, same behavior.
> However, the query works normally (single row, PK IDX scan) on N0, A,
> N1, and C.
That likely is related to the collation definitions differing between
the systems. Note that the systems where it doesn't work are Debian 10,
whereas the rest is Debian 9.
See https://wiki.postgresql.org/wiki/Locale_data_changes
Greetings,
Andres Freund