In a where clause, the equals operator doesn't work well for basic queries.

[DavidPerezIngeniero]

11.7-alpine version exhibits this strange behaviour:

# select '[' || lis_lis || ']' from imalis where lis_lis like 'PME_USU_00'; 
   ?column?   
--------------
 [PME_USU_00]
(1 row)

whereas:

# select '[' || lis_lis || ']' from imalis where lis_lis = 'PME_USU_00'; 
 ?column? 
----------
(0 rows)

Non-Docker Postgres 11 shows consistent results with exactly the same data (rsync'ed), i.e., 1 row of results for both selects.

lis_lis is a varying char(20) column that is the primary key of the table.
Using:

• amd64
• Docker version 19.03.6-ce, build 369ce74
• Host is Amazon Linux.

[DavidPerezIngeniero]

Tags 11.6-alpine and 11.5-alpine also have the same bug.

[wglambert]

Do you know if it does this in the non-Alpine variant too?

[DavidPerezIngeniero]

I cannot test because the debian variant doesn't support the es-ES.UTF-8 locale.

[DavidPerezIngeniero]

Confirmed that Debian variant works ok.
So this is a bug in the Alpine specific variant.

[wglambert]

Yeah it doesn't seem like something we can change at our level, probably have to file it upstream somewhere

https://github.com/docker-library/docs/tree/master/postgres#postgresversion-alpine

The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements.

[yosifkit]

Seems related to #327