LZ4 is configured during compilation, but not available when querying the docker container
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Inspect 16-alpine3.19/Dockerfile around line 124, then reproduce the CREATE TABLE statement in the postgres:16-alpine container using the shown docker-compose configuration. Compare the image's build configuration with the running server's reported compression capabilities. Done means identifying whether the image or runtime setup prevents LZ4 support and documenting the required change.
Written by the indexing model from the issue text.
Description
Hello,
I am using the 16-alpine image for a docker container. I am using alpine specifically because lz4 appears to be enabled during compilation of the docker image. However, when I connect to the docker container and write SQL that depends on lz4 I get this error:
ERROR: compression method lz4 not supported
DETAIL: This functionality requires the server to be built with lz4 support.
HINT: You need to rebuild PostgreSQL using --with-lz4.
SQL state: 0A000
However, in the dockerfile, LZ4 compression is enabled
https://github.com/docker-library/postgres/blob/ce5bf6e7eb8f339b2a8561bf8fb5fe5d4e8c96aa/16/alpine3.19/Dockerfile#L124
Here is an example SQL query I am trying to run:
CREATE TABLE my_table (
...
id bigint GENERATED ALWAYS AS IDENTITY,
data text COMPRESSION lz4,
...
);
Is there some additional configuration I need to pass into the docker container?
Here is a snippet of the docker-compose
postgres:
image: postgres:16-alpine
container_name: my_postgres
environment:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
POSTGRES_DB: postgres
volumes:
- type: bind
source: ../..
target: /my_dir
ports:
- "5432:5432"
I have also downgraded and tried with 15.5-alpine.
- Dominant language
- Shell
- Stars
- 2.5k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker-library/postgres
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
docker-library/postgres#1420 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
docker-library/postgres#1419 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
docker-library/postgres#1389 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
docker-library/postgres#1356 · 5 comments · 7 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
docker-library/postgres#1355 · 10 comments · 11 reactions ·
All issues in docker-library/postgres
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100