Please upgrade TimescaleDB to 2.6.1
Closed this issue · 6 comments
Describe the bug
Seeing a lot of
2022-04-16 00:26:31.736 UTC [12438] LOG: the "timescaledb" extension is not up-to-date
2022-04-16 00:26:31.736 UTC [12438] HINT: The most up-to-date version is 2.6.1, the installed version is 2.6.0.
in the addon log.
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.
Hi @bjornbak,
These new versions keep coming! :) I'll try to keep up.
My first priority is to make sure everybody is succesful in upgrading to Postgresql 14.
Hi @bjornbak,
These new versions keep coming! :) I'll try to keep up. My first priority is to make sure everybody is succesful in upgrading to Postgresql 14.
I had issues with pgsql 14 too.
Added
init_commands:
- >-
sed -i "s/#password_encryption = md5/password_encryption = md5/"
/data/postgres/postgresql.conf
Hi @bjornbak , can you elaborate on that last command further?
Why did you need to change the md5 enctryption?
Oh BTW,
these messages
'
2022-04-16 00:26:31.736 UTC [12438] LOG: the "timescaledb" extension is not up-to-date
2022-04-16 00:26:31.736 UTC [12438] HINT: The most up-to-date version is 2.6.1, the installed version is 2.6.0.
'
are not fatal.
I bump versions every half year or so. I'm trying to maintain a balance between stability and new versions / functions.
Why did you need to change the md5 enctryption?
It is a long time ago but think the issue is the default is changed so I need to tell explicitly that I want md5.
Alright, a new releae is out!
Should this issue still persists, please reopen!