Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e1KR4-0004Mz-5V for pgsql-pkg-yum@arkaria.postgresql.org; Sun, 08 Oct 2017 22:52:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e1KR2-0007zz-RF for pgsql-pkg-yum@arkaria.postgresql.org; Sun, 08 Oct 2017 22:52:36 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e1KR2-0007zn-Bb for pgsql-pkg-yum@postgresql.org; Sun, 08 Oct 2017 22:52:36 +0000 Received: from mail-it0-x233.google.com ([2607:f8b0:4001:c0b::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e1KQy-0003wV-Ch for pgsql-pkg-yum@postgresql.org; Sun, 08 Oct 2017 22:52:34 +0000 Received: by mail-it0-x233.google.com with SMTP id 72so10489651itk.3 for ; Sun, 08 Oct 2017 15:52:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=GH0atwf8kzJScsMddHbvzInb40MZTotpP0Ky6Yj7QNw=; b=efgzLaijFaNniaMOpVwzZ3npG9Wp3x6ht32vxoDpl+NwR7oE27UeGruIfQDYVfbdkx 8aGGtl8Pg4x/ynet5UXNiCI+skpnx4fZuwzTDxDn9TbqrFF8PUnYSJBFslybhrbkVSpr C0GK9Nm6ojAa6Fx6qORF/ekuYmj4aaX8vszbsTfa4TPfaLDhJFad1upbI0oKfrWdYxhZ usAWgFZHTh0wbY4G/9rBveA8yNyjV/84cyIwKuEEBR40PjZoviPTPthBDbt0fv2sH2Np e2+jcWMvpt/GD3K6P4IM2w/lmia5EyOPCKGV4hKEHKMVVEok4xAMoaNAYG/WRg+spacw rYCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=GH0atwf8kzJScsMddHbvzInb40MZTotpP0Ky6Yj7QNw=; b=TkFknDGLqeanoHJO77SAzmF7/dt3J3BrBf7GHyNMGUql9rwXVddIDPiOnKlwFx0Vyi iOxHEVrpQXziGjntzpVodAlE0ftN5ApCnEIuFhoN6j1/KwBcJEzRHCuWGRg2v3JzCkKe Q/oAoVYIoukz5NMxIzc1HGp+9YbGd1Qb9e3sBw/VvAQD/NxNV5KiM87CCKjzQl3USgzk xxx6jKNAutsgcnK/ezGOTlAHjFaXFk6k349KXOMTZA6TIhdGU9m8t0FSB5ZHOiCG9dIz i47DN3f7TdGUammy2dJC7bZsJmD/TCFVrGnnNAbfnCfEB14mivtXUBxeYC8d8bnhon5k 7FIg== X-Gm-Message-State: AMCzsaUroks4v5w2D0QbNLFEEt52LVEwRpKHk2rf4Ppsmb7sfVkc4hn/ uEP4G/J7IG7fAi1ZqnmeBLJ74w== X-Google-Smtp-Source: AOwi7QAuyFp9iLIvUskCZKd2yuKqXb82Fyk5y9T2BaVP+KwvIULCUiC98OjW1jciqtCbB+vpa+zZvA== X-Received: by 10.36.194.193 with SMTP id i184mr10908334itg.139.1507503151159; Sun, 08 Oct 2017 15:52:31 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id k76sm3350607ita.4.2017.10.08.15.52.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Oct 2017 15:52:30 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 6F059801116; Sun, 8 Oct 2017 17:52:29 -0500 (CDT) Date: Sun, 8 Oct 2017 17:52:29 -0500 From: Justin Pryzby To: pgsql-pkg-yum@postgresql.org Cc: Jimmy Angelakos Subject: postgis24_* package Message-ID: <20171008225229.GH25298@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-pkg-yum Precedence: bulk Sender: pgsql-pkg-yum-owner@postgresql.org Just curious how the postgis package upgrades are intended to work ? It seems to me we need to (for example) install postgis24_96, then run postgis_upgrade.sql (or UPGRADE EXTENSION). It looks like PG10 only supported by postgis24 packages, so that's a needed step in pg_upgrade to PG10 (else PG upgrade will die after pg_dump --section=pre-data with an error in loadable_libraries.txt0 Ideally the package would be installable alongside postgis23_96, to avoid backends being unable to load postgis library (or loading an incompatible library, crashing, taking down the server and rest of the backends). However they're not co-installable: [pryzbyj@database ~]$ rpm -qa |grep postgis postgis23_96-2.3.3-1.rhel6.x86_64 [pryzbyj@database ~]$ sudo yum install postgis24_96 file /usr/pgsql-9.6/lib/liblwgeom.so from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/address_standardizer.control from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/address_standardizer.sql from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/address_standardizer_data_us.control from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/postgis.control from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/postgis_tiger_geocoder.control from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/postgis_tiger_geocoder.sql from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 file /usr/pgsql-9.6/share/extension/postgis_topology.control from install of postgis24_96-2.4.0-1.rhel6.x86_64 conflicts with file from package postgis23_96-2.3.3-1.rhel6.x86_64 Okay, if they're no co-installable, that's fine. But why does the package name include the postgis version then ? For the postgresql96 style package names, that was to allow co-installation. Further, how do I actually install postgis24_96 ? Do I actually have to run "rpm -e postgis23_96" first ? Or is some particular yum incanatation intended to handle that ? I'm more familiar with Debian's packages, where the file overlap would've been declated with "Conflicts" metadata (probably against a postgis-postgresql96 virtual package). And file being allowed to be replaced would've been declated with "Replaces" (but maybe not here, since it can and will cause the server to crash). And "Conflicts+Replaces" would've been declared to allow installing postgis24_10, but requiring the removal of the old package. I think conflicts alone is sufficient and ideal for this purpose. https://www.debian.org/doc/debian-policy/#conflicting-binary-packages-conflicts Under debian I would do "apt-get install postgis23_96- postgis24_10" to remove one and install the other. I found yum has this syntax: "sudo yum install -- -postgis23_96 postgis24_10", but it seems that means "cancel installation sugggested by previous dependency/recommends/groupinstall" rather than "uninstall". Is there a variation requiring removal ?? BTW this page still talks about PG10 beta: https://yum.postgresql.org/ Also there's a stray/missing quote in the mailto link on this page: https://yum.postgresql.org/news-10beta-ready-for-testing.php ">us Thanks, Justin -- Sent via pgsql-pkg-yum mailing list (pgsql-pkg-yum@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-yum