pg_dump: error :aborting because of server version mismatch about dsmr-reader-docker HOT 11 CLOSED

Fixed!

from dsmr-reader-docker.

Yeah, I've tried to upgrade to the latest client recently, but it gave errors.
Let me try again as some dependencies caused issues.

from dsmr-reader-docker.

Hi, late reply, but this should be fixed in the release created Today.

from dsmr-reader-docker.

Hi, thank you for your work :-)
Unfortunately, with the latest version (tag 5.10.4-2023.11.01) there is still a mismatch between the server and pg_dump version:
2023-11-24 08:21:23,444 ERROR schedule execute_scheduled_processes 39 | (OSError) dsmr_backup.services.email.run errored: b'pg_dump: error: aborting because of server version mismatch\npg_dump: detail: server version: 16.0; pg_dump version: 15.5\n' pg_dump: error: aborting because of server version mismatch pg_dump: detail: server version: 16.0; pg_dump version: 15.5

I'm using your image on MicroK8s v1.28.3

Kinds regards,
Casper

from dsmr-reader-docker.

Hi, thanks! Yes, and unfortunatly I`m dependent on the pg client releases Alpine adds to their release.
In this case (Alpine 3.18), only supports PG up to v15.

https://pkgs.alpinelinux.org/packages?name=postgresql*-client&branch=v3.18&repo=&arch=&maintainer=

However, it seems that you have some knowledge regarding this topic (based on MicroK8s usage). You could try to build your own image based on the Edge image of Alpine. If wanted, I'm happy to help. Before releasing I often use podman to build locally.The biggest challange with Alpine are the dependencies, also in regards to Python. Anyway, nothing that can't be solved :).

Ofcourse another option would be to switch to PG15 server. EOL date is still 3 years from now, and compatibility with other tools and products is still better compared to PG16.

from dsmr-reader-docker.

Hi, thank you for your suggestions. I've decided to take the easy route and downgraded postgres to 15.5-alpine3.18 which resolves the issue. I didn't pay attention to the pg16 release date and didn't notice it was still bleeding edge (at least from the alpine point of view). I recognize the alpine dependency troubles, so I chose the easy way out :-)
Thanks again.
Kind regards,
Casper

from dsmr-reader-docker.

Great! I believe you've made the best choice. It would have been different if PG15 would be EOL soon. PG16 is just there for a couple of months, so better wait for a bit to migrate indeed.

from dsmr-reader-docker.

I ran into the same issue. Will perform a downgrade of PG as well.
@xirixiz May I suggest to put this limitation in the Technologies section of the README.md?
I recently built a new environment myself and did check the README. Didn't see any limitations so went with the latest version of PG only then to find out about the pg_dump version mismatch.

from dsmr-reader-docker.

But there is ... https://github.com/xirixiz/dsmr-reader-docker#technologies

Maybe I`m able to share a bit more info in the README regarding this topic.

from dsmr-reader-docker.

Yeah, what I meant is extending that part a little bit. It shows minimum versions now, like Postgres >= 13.x
But that suggests 16 is also fine. Maybe something like Postgres >= 13.x AND <= 15.x
That could then be updated after successfully testing a new major version in the future.

from dsmr-reader-docker.

Oh yeah, you're right hehehe.... it was meant differently. I`ll fix the README. Thanks!

from dsmr-reader-docker.