@Sempf its the same basic server as our current database, but the current one only has 256GB of ram and 2x4TB drives. Oh, it also has 10g Ethernet to connect to the app servers.
@SpaceLifeForm there will be some downtime. To take advantage of some of the benefits from moving to postrgresql 16, I have to run a dump from the old database and import into the new database. That’ll take probably 2 hours or so
Since we recently we recently had 2+ hours of downtime, I will allow it. /s
TBH, I would do the downtime because if there is a problem, you will be able to fallback quickly.
You want to failfast.
If you try the migration path, there could be an undetected ptoblem ocuuring that is not discovered quickly, and the remediation could end up being a bigger mess than 2 hours of downtime.