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