Update the EXPECTED_DATABASE_VERSION to 17

[khdevel]

Hello,

I noticed that Web3Signer wants to use quite pretty old Postgres version which is 12. The EOL reached it on November 21, 2024. Would you please consider update the service to support the newest versions like 15, 16, 17. We have 2026 now...

It seems to be related to the #988

[usmansaleem]

@khdevel This EXPECTED_DATABASE_VERSION variable is for internal Web3Signer schema changes tracking. In other words, if Web3Signer has some database schema changes, this version would be changed in the code and you are expected to run schema upgrade scripts which will also update this version in database_version table. We perform check at Web3Signer startup that the version in table database_version matches with the version declared in the code, and abort the startup if mismatch happens. This has nothing to do with PostgreSQL version. Our test environments may be running a slightly older version of the PostgreSQL than the latest available version, however, Web3Signer should still be compatible with latest PostgreSQL version as we bundle latest (42.7.8) PG JDBC driver which should support all recent versions of PostgreSQL.

Please reopen the issue if you have more queries.

[khdevel]

okay, thank you for the clarification. I was confused that after I run the service and connect it to PG v17 the logs show that this version is not compatible. I will check it again.