From owner-freebsd-ports-bugs@freebsd.org Mon Mar 6 11:36:07 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51B4DCFBE27 for ; Mon, 6 Mar 2017 11:36:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 368ED101D for ; Mon, 6 Mar 2017 11:36:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v26Ba6HC097532 for ; Mon, 6 Mar 2017 11:36:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 217515] [exp-run] Update PostgreSQL default version to 9.5 Date: Mon, 06 Mar 2017 11:36:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Ports Framework X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: tz@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: portmgr@FreeBSD.org X-Bugzilla-Flags: exp-run? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2017 11:36:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217515 --- Comment #4 from Torsten Zuehlsdorff --- > 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.=