Skip to content
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

After upgrading 2.18.0 to 2.18.1 with existing database container fails to start because of USE_FLOAT8_BYVAL #299

Closed
darthmaim opened this issue Feb 11, 2025 · 3 comments

Comments

@darthmaim
Copy link

When upgrading the docker image from 2.18.0-pg17 to 2.18.1-pg17 with an existing database, timescale fails to start with the following error:

PostgreSQL Database directory appears to contain a database; Skipping initialization

[1] FATAL:  database files are incompatible with server
[1] DETAIL:  The database cluster was initialized with USE_FLOAT8_BYVAL but the server was compiled without USE_FLOAT8_BYVAL.
[1] HINT:  It looks like you need to recompile or initdb.
[1] LOG:  database system is shut down

Downgrading to 2.18.0-pg17 makes the container start again.

@darthmaim
Copy link
Author

Looks like it is the same issue as docker-library/postgres#1195.

Looking at https://hub.docker.com/r/timescale/timescaledb/tags?name=2.18.1-pg17 only linux/arm/v6 is published yet, all the other architectures are still missing.

This will probably fix itself once the remaining architectures are pushed.

@svenklemm
Copy link
Member

Does this work now with the docker images published?

@darthmaim
Copy link
Author

Yes, its working again, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants