Refactor to support Postgres greater than 11

[childers]

Hi all,

Postgres 11 is EOL November 2024, and I am worried that this deadline is coming up fast. We've been working on refactoring multiple aspects of the code, but have not been able to get Apollo working on any Postgres version greater than 11.

I would love Apollo to support up to 15, but anything higher than 11 would give us more time.

[cmdcolin]

development effort is geared towards apollo 3 right now, but we certainly would accept PRs to this repo if you have any. if you can post the specific issues that cause it to not work with newer versions of postgres, may also be able to advise

[ChrisChilders-USDA]

@cmdcolin @ihh Postgres 11 is EOL. Can we discuss What this means for the Apollo project? We have hard limits on using software that is EOL, as I'm sure other users in government and security conscious IT groups do as well.

I'd also like to reference the issue about this that was opened in 2019. It has more specifics about the actual issue.
#2336

[hexylena]

Just copying my comments from the email thread here, to share with everyone.

We're on 13.11, with no modifications to make it work. Running a bog standard build of apollo (just a few plugins).

If memory serves this machine used to be ~9 but they upgraded it using the standard postgres upgrade procedures, and we've had no issues since the upgrades. (i.e. I don't believe they dumped/re-loaded, rather just the apollo db migrations were run on the original database, and it's progressed through database versions since then.)

edit: posted some more on #2336 (comment)