Re: Another morning lost to bad ports choices (perl upgrade, plus postgres)
- Reply: Julien Cigar : "Re: Another morning lost to bad ports choices (perl upgrade, plus postgres)"
- Reply: Piotr Smyrak : "Re: Another morning lost to bad ports choices (perl upgrade, plus postgres)"
- In reply to: Dan Mahoney (Ports): "Another morning lost to bad ports choices (perl upgrade, plus postgres)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 12 Dec 2023 12:01:23 UTC
On 2023-10-24 15:12, Dan Mahoney (Ports) wrote: > Yes, I know that I should be ready to upgrade to 15 at some point, on > whatever quarterly port boundary it's decided, "I guess that's when", > with no advance notice, via the full stupid dump-and-restore > process. I know it's too late now, but run postgresql-server in its own jail. Among other administrative advantages, it splits the postgresql-client dependency tree so you don't have to upgrade your database server every time the Ports Tree bumps PGSQL_DEFAULT. PostgreSQL clients tend to have excellent backward compatibility, so as a rule the server just needs to be a supported version.