Date: Tue, 07 Mar 2017 16:10:30 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 217515] [exp-run] Update PostgreSQL default version to 9.5 Message-ID: <bug-217515-13-Qu3iBEUHiY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217515-13@https.bugs.freebsd.org/bugzilla/> References: <bug-217515-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217515 --- Comment #9 from Torsten Zuehlsdorff <tz@freebsd.org> --- It seems you all reading me wrong! I'm not in favor of breaking thinks. I'm annoyed but that regularly, therefore the mention of other breakage. Heck, i have an 11 TB PostgreSQL cluster. That is nothing you just dump and restore= ... My point is: there is currently no (automatic) update path for PostgreSQL. There could be probably one when we are going to PostgreSQL 9.6, but this w= ill break things also. Not going to 9.6 will break other things. So, yes: breaking (especially a database) is a big no-go. But nobody mentio= ned even a possibility currently supported! Nobody raised, that the configuration between PostgreSQL versions are often incompatible. Let alone multiple changes in behavior causing problems. Nobo= dy mentioned that it is a really bad idea to update things automatically too. The update of the default version is a loss in any way. It will break thing= s no matter what you do. (I still have hope somebody proves me wrong. Please!) We just can argue with worse situation is not as worse as the other one. Best way would be to allow installation of two different versions, which wo= uld enable pg_migrate usage. But this need PostgreSQL 9.6, which will break thi= ngs through the renamed username. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217515-13-Qu3iBEUHiY>