-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Unexpected behaviour in select clause when using apline image #273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This sounds similar to #276 😞 I wonder if musl is doing something odd? Can it be reproduced with the Alpine package (if it can be, we'll have to punt to upstream, but otherwise we can look at what they're doing that we aren't 😄)? |
Had the same problem, noticed it when unique constraints were no longer checked. Switched from the standard "big" image to the lightweight one using the same filesystem for the postgresql folder. Any information I can provide that would help ? |
Can it be reproduced with the Alpine package (assuming you are using a similar enough version of PostgreSQL as the Alpine package, 9.6.2)? I don't have any data to test the problem. $ docker run -it --rm -e PGDATA=/var/lib/postgresql/data -v /current-db/:/var/lib/postgresql/data alpine:3.6
$ apk add --no-cache su-exec postgresql
$ mkdir /run/postgresql/
$ chown postgres:postgres /run/postgresql/
$ # not required if you already have a db to test on
$ su-exec postgres:postgres initdb
$ su-exec postgres:postgres postgres &
$ psql -U postgres
$ # tests! |
Unable to reproduce, closing old issue. |
If you use the docker alpine image, String matches in the
where
clause seems not to work correctly. This was discovered by debugging a strangely behaving davical calendar server:Using the "normal" (non-alpine) image fixes the problem.
The text was updated successfully, but these errors were encountered: