Date: Wed, 08 Mar 2017 09:46:11 +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-EYi2pLL139@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 #14 from Torsten Zuehlsdorff <tz@freebsd.org> --- (In reply to Mathieu Arnold from comment #6) > I have not used dump/restore since pre 8.4 days, pg_upgrade works just fi= ne, but=20 > you have to have the old and new servers installed at the same time. > Of course it does not work with the way we currently do things, but this = is=20 > mostly because people are quite happy with breaking everyone's setups eac= h time=20 > the default changes.=20 Just one important point: it is *not* a good idea to do pg_upgrade automatically. I believe with the changes done in PostgreSQL 9.6 by girgen = it should be possible to use pg_upgrade much easier. But as stated previous: automatic update is a bad idea. Behavior changes, functions are removed and so on. And since you bring the point up: we really need to do something against the breakings. Even as a port committer i'm not able to cope with the last brea= ks anymore. I just have two options left: pkg lock and hope best for the rest = or do not upgrade at all. That is very very bad... @Chris: I wont stop you - but i did not understand your solution proposal either ;)= Can you please make it more clear? Or do you want to just create a prototype for testing and show it to us? --=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-EYi2pLL139>