From owner-freebsd-ports-bugs@freebsd.org Tue Mar 7 15:18:19 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 0268DD01027 for ; Tue, 7 Mar 2017 15:18:19 +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 C26A5145A for ; Tue, 7 Mar 2017 15:18:18 +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 v27FIIUg044682 for ; Tue, 7 Mar 2017 15:18:18 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: Tue, 07 Mar 2017 15:18:18 +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: portmaster@bsdforge.com 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: cc 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: Tue, 07 Mar 2017 15:18:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217515 Chris Hutchinson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |portmaster@bsdforge.com --- Comment #7 from Chris Hutchinson --- (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 you have to have the old and new servers installed at the same time. >=20 > Of course it does not work with the way we currently do things, but this = is > mostly because people are quite happy with breaking everyone's setups each > time the default changes. And because nobody on pgsql@ wants to take a d= ay > to figure out how to do it correctly. OK. What follows is off the top of my pointy little head. But... I think it's going to be POLA no matter which/any direction is chosen. But the first couple of things that come to mind are chroot(8), of even creating a port that facilitates the entire process. Those with any sizable DB (should) understand the maintenance costs, already. But seems to me the simplest solution; in the short term, anyway; is chrooting the proposed new version, and finally moving it into it's final destination. While I's early. I haven't finished my first cup of coffee, and haven't completely thought this through; am I completely off the map? --Chris --=20 You are receiving this mail because: You are on the CC list for the bug.=