From owner-freebsd-questions@freebsd.org Wed Jan 20 19:09:32 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 9267F4FF349 for ; Wed, 20 Jan 2021 19:09:32 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DLZp34wzlz3jL0 for ; Wed, 20 Jan 2021 19:09:31 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 997F97C760 for ; Wed, 20 Jan 2021 13:09:24 -0600 (CST) Received: by mail.geeks.org (Postfix, from userid 1003) id 8DDF17C7CE; Wed, 20 Jan 2021 13:09:24 -0600 (CST) Date: Wed, 20 Jan 2021 13:09:24 -0600 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: pkg solver question Message-ID: References: <6037e872-08c2-9d13-4cfc-bab9c856dd22@kicp.uchicago.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6037e872-08c2-9d13-4cfc-bab9c856dd22@kicp.uchicago.edu> X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4DLZp34wzlz3jL0 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of merlyn@geeks.org designates 2001:4980:3333:1::1 as permitted sender) smtp.mailfrom=merlyn@geeks.org X-Spamd-Result: default: False [-3.30 / 15.00]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:4980:3333:1::1:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2001:4980:3333:1::1:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[geeks.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7753, ipnet:2001:4980::/32, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-questions] 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:09:32 -0000 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 > long time, do I do know to migrate postgresql to new version postgresql > way. There is postgresql command for that: > > pg_upgrade > > to successfully use that command you do need both older postgresql > version binaries (and libraries), and new ones to exist on your machine > simultaneously. And you do have to have enough space for postgresql old > and new data... Which can't happen if you use pkg binaries, because they are exclusive... 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.. postgresql tends to get 'pkg lock' on my machines until I want to look/deal with it. 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). 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.