Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Mar 2017 11:36:07 +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-ca77lOgnwj@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 #4 from Torsten Zuehlsdorff <tz@freebsd.org> ---
> Now, with packages, people run pkg upgrade, and they will kill you if you=
=20
> break their setup.
>
> I know there was no upgrade path before, but for the previous bumps, it w=
as not=20
> important.
>=20
> One must now be written, and thoroughly tested *before* the version can b=
e=20
> bumped.

While i really support your point, i have to disagree: we break things on a
regular basis. Have a look at UPDATING. Its - very sadly - normal to break
things and just put a short notice in this file. Within the last 1 or 2 mon=
ths
the xorg-update killed my laptop and the qt update my GitLab. And i can cou=
nt
various more.

The current status of the portstree just do not allow any automatic way of =
not
breaking PostgreSQL with an update. I really hope someone will jump in and
correct me, but as far as i know the work of girgin on PostgreSQL 9.6 just
makes the ground for an improvement to such update-path.

So, the only available update path currently is:

pg_dumpall -> dumps the complete database
shutdown the database
remove /usr/local/pgsql/data (really)
update to new version
initdb new cluster
restore the dump

This works and is quite frustrating, especially if your database has a size=
 of
multiple TB. :/ We can put such a description in UPDATING, but things will
break (like previous).

--=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-ca77lOgnwj>