PostgreSQL 15 update

[pfaffman (Jay Pfaffman)]

@Firepup650

.s.PGSQL.50432"

So somewhere you changed the postgres port to 50432 instead of 5432? (OR maybe the migration code does that and I’ve never noticed).

Maybe switch to the postgres13 template as suggested in the OP? And if that works, what I would do is move to a new server and avoid the whole transition-to-new-postgres-version issue and just restore the database to the new server.

[Firepup650 (Firepup Sixfifty)]

@pfaffman

So somewhere you changed the postgres port to 50432 instead of 5432? (OR maybe the migration code does that and I’ve never noticed).

I didn’t change it, and that socket does exist so…

@pfaffman

Maybe switch to the postgres13 template as suggested in the OP?

I did that for now, but I assume that’s a bad idea long-term

@pfaffman

And if that works, what I would do is move to a new server and avoid the whole transition-to-new-postgres-version issue and just restore the database to the new server.

I’ll let the one who manages the server know ig

[pfaffman (Jay Pfaffman)]

@Firepup650

I didn’t change it

So maybe it does run two postgres to make the move.

@Firepup650

I assume that’s a bad idea long-term

True, but I’m relieved that your back up!