Обсуждение: PostGIS packages should not remove older libs
Devrim, Jeff: The current pgdg RPMs for PostGIS remove the older .so files when you upgrade PostGIS. This is bad policy because it forces the user to shut down the database application in order to upgrade PostGIS. If the older libs are left in place, you can do an online upgrade of PostGIS without a downtime. Please change the RPMs so that they do not remove the older .so files when you upgrade. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com
Hi, On Tue, 2014-09-16 at 14:00 -0700, Josh Berkus wrote: > The current pgdg RPMs for PostGIS remove the older .so files when you > upgrade PostGIS. This is bad policy because it forces the user to > shut down the database application in order to upgrade PostGIS. If > the older libs are left in place, you can do an online upgrade of > PostGIS without a downtime. > > Please change the RPMs so that they do not remove the older .so files > when you upgrade. Can you please clarify this for me? Do you mean that we should keep .so files of 2.1.3 , when someone upgrades to 2.1.4? Regards, -- Devrim GÜNDÜZ Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Вложения
> On Sep 21, 2014, at 12:40, Devrim Gündüz <devrim@gunduz.org> wrote: > > Can you please clarify this for me? Do you mean that we should keep .so > files of 2.1.3 , when someone upgrades to 2.1.4? I think he means when going from 2.0 to 2.1.
On 09/21/2014 12:49 PM, Jeff Frost wrote: > > >> On Sep 21, 2014, at 12:40, Devrim Gündüz <devrim@gunduz.org> wrote: >> >> Can you please clarify this for me? Do you mean that we should keep .so >> files of 2.1.3 , when someone upgrades to 2.1.4? > > I think he means when going from 2.0 to 2.1. Correct. The postgis-#.#.so libraries are designed to be present side-by-side so that users can do an online upgrade. But if postgis-2.0.so gets deleted as soon as 2.1 is installed, then an online upgrade isn't possible. It also messes with replication to have the 2.0 library deleted, should you upgrade the replica before the master, as is common. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com