Postgresql update

[immauss]

As some of you may know, postgresql 13 goes EOL this month. . . . .

I only just realized this ...

The current image is based on pg13 as that was the default in Debian Bookworm when I migrated to it. Very soon (hopefully within the next few days, it will be possible to upgrade the container's database to pg15. There are some distinct advantages to this, but the big one is that 15 is not EOL . . . .

So ... the plan is:

• Until early January, v13 will remain the default, with an option to upgrade to 15.
• In early January, v15 will become the default and force the upgrade from 13.
• in early March, v13 will no longer be available in the image.

If for some reason this is a problem for you, please speak now ......

Thank you,
-Scott

[immauss]

Life rather got in the way ...
So ... I'm only just completing this. As of 25.12.26.01 (releasing today) an upgrade to postgresql 15 will be possible by setting the PGVER=15 environment variable in your docker-compose.yaml or via -e PGVER=15

[dustinbird]

Happy new year.

I just wanted to check whether I should be seeing Postgres15 in my image now. I have updated the compose file (see attached) but I am still only seeing a 13 folder in /lib/postgres after applying the change.

Compose file attached.
Compose SMIW2.txt

[immauss]

Hmmm ....
@dustinbird

Can you try immauss/openvas:25.12.26.01

I think the one that is still "latest" was missing something.

I found it during the holidays, but looks it was not published as latest yet.

I had some major setbacks/time sinks from late Nov until about 3 or 4 days ago, so the time line suggested in the OP will need to slip to the right a bit. I'll try to get a new schedule published in the next week or so.

Thanks,

-Scott

[dustinbird]

Thank you Scott,

I will try and have a look into that build.

I am not so worried about the timeframe for release, I was just more concerned I had missed something in my config that was stopping this from showing. I will force the version you mentioned on a test box to see how this looks.

[dustinbird]

I can confirm with the 25.12.26.01 build I can see both the 13 and 15 folders within Postgres. I have this running on one of the boxes now.

[immauss]

Bumping this to hopefully raise awareness. I've had to adjust the schedule due to .... well ... life.

I've done tons of testing for the auto-upgrade, and all seems to be working well. If you have any problems, please open an issue at:
https://github.com/immauss/openvas/issues

So ... the new plan is:

Until 31 March, v13 will remain the default, with an option to upgrade to 15.
Shortly after 31 March, v15 will become the default and force the upgrade from 13.
in early Mid April, v13 will no longer be available in the image.

If for some reason this is a problem for you, please speak now ......