From owner-freebsd-questions@freebsd.org Wed Jan 20 19:42:26 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AAB454D84BD for ; Wed, 20 Jan 2021 19:42:26 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 4DLbX2056xz3lLY for ; Wed, 20 Jan 2021 19:42:25 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from [128.135.52.198] (unknown [128.135.52.198]) (Authenticated sender: galtsev) by kicp.uchicago.edu (Postfix) with ESMTPSA id 687154E652; Wed, 20 Jan 2021 13:42:25 -0600 (CST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: pkg solver question From: Valeri Galtsev In-Reply-To: Date: Wed, 20 Jan 2021 13:42:25 -0600 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <74412AF1-97F7-4ED2-BDA9-286212E66B41@kicp.uchicago.edu> References: <6037e872-08c2-9d13-4cfc-bab9c856dd22@kicp.uchicago.edu> To: Doug McIntyre X-Mailer: Apple Mail (2.3608.120.23.2.4) X-Rspamd-Queue-Id: 4DLbX2056xz3lLY X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=uchicago.edu (policy=none); spf=none (mx1.freebsd.org: domain of galtsev@kicp.uchicago.edu has no SPF policy when checking 128.135.20.70) smtp.mailfrom=galtsev@kicp.uchicago.edu X-Spamd-Result: default: False [-2.40 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RBL_DBL_DONT_QUERY_IPS(0.00)[128.135.20.70:from]; SPAMHAUS_ZRD(0.00)[128.135.20.70:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:160, ipnet:128.135.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-questions]; DMARC_POLICY_SOFTFAIL(0.10)[uchicago.edu : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2021 19:42:26 -0000 > On Jan 20, 2021, at 1:09 PM, Doug McIntyre wrote: >=20 > On Wed, Jan 20, 2021 at 12:06:20PM -0600, Valeri Galtsev wrote: >> It is worth warning, indeed. Luckily for me I use postgresql for = really=20 >> long time, do I do know to migrate postgresql to new version = postgresql=20 >> way. There is postgresql command for that: >>=20 >> pg_upgrade >>=20 >> to successfully use that command you do need both older postgresql=20 >> version binaries (and libraries), and new ones to exist on your = machine=20 >> simultaneously. And you do have to have enough space for postgresql = old=20 >> and new data... >=20 >=20 > Which can't happen if you use pkg binaries, because they are = exclusive... >=20 To tell you the truth, I did it =E2=80=9Csimple guy=E2=80=99s way=E2=80=9D= . I copied binaries and libraries of older version of postgresql into /usr/local/oldpostgresql the list of all files in the package can be obtained as usually by: pkg info -l [package name] After that I did upgrade, and used pg_upgrade. > There is actually a warning that you'll need a database upgrade.... > Which comes _AFTER_ all the old stuff has been removed, and the new > installed, and potentially have broken your existing DB files.. Nope. Old postgresql data stays intact when old postgresql-server = package is removed. Pkg maintainers for postgresql are really good about = everything in my observation. But as always, backup everything before starting any changes. Just my $0.02 Valeri > postgresql tends to get 'pkg lock' on my machines until I want to = look/deal with it. >=20 > Same with syslog-ng (which randomly requires you to touch the config > file and increment the version # of it or the service refuses to > start), and courier-imap (which had a major change from 4.x to 5.x > that broke everything without you fixing up every single mail folder > on your server by hand (with a utility), and changes it's behavior to > be 8-bit right by the standards, but not compatible). >=20 > I do wish there was a way to have pkg have multiple versions > installed. And a way for the pkg repos to keep old versions around > instead of being replaced when built. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org"