Date: Wed, 20 Jan 2021 13:09:24 -0600 From: Doug McIntyre <merlyn@geeks.org> To: freebsd-questions@freebsd.org Subject: Re: pkg solver question Message-ID: <YAh/5JDE6NfDRHX0@geeks.org> In-Reply-To: <6037e872-08c2-9d13-4cfc-bab9c856dd22@kicp.uchicago.edu> References: <CAFuo_fwh7gar7LCRLEnSeEu24QEe=hwZ0QZkaGVoNPozh8Rd3g@mail.gmail.com> <6037e872-08c2-9d13-4cfc-bab9c856dd22@kicp.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YAh/5JDE6NfDRHX0>