From owner-freebsd-ports-bugs@freebsd.org Wed Mar 8 09:46:15 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 E7661D02DE3 for ; Wed, 8 Mar 2017 09:46:15 +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 D6E851B6C for ; Wed, 8 Mar 2017 09:46:15 +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 v289kB3Y015898 for ; Wed, 8 Mar 2017 09:46:15 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: Wed, 08 Mar 2017 09:46:11 +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: Wed, 08 Mar 2017 09:46:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217515 --- Comment #14 from Torsten Zuehlsdorff --- (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.=