On Tue, Aug 11, 2020 at 02:58:30PM +0200, Magnus Hagander wrote: > On Tue, Aug 4, 2020 at 11:42 AM Dave Page <dp...@pgadmin.org> wrote: > That would require fairly large changes to the installer to allow it to > login to the database server (whether that would work would be dependent > on > how pg_hba.conf is configured), and also assumes that the ICU ABI hasn't > changed between releases. It would also require some hacky renaming of > DLLs, as they have the version number in them. > > I assumed it had code for that stuff already. Mainly because I assumed it > supported doing pg_upgrade, which requires similar things no?
While pg_upgrade requires having the old and new cluster software in place, I don't think it helps allowing different ICU versions for each cluster. I guess you can argue that if you know the user is _not_ going to be using pg_upgrade, then a new ICU version should be used for the new cluster. -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
