Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYQ6x-001e9z-38 for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2023 12:03:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qYQ6v-000KOY-NO for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2023 12:03:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYQ6v-000KOP-9n for pgsql-admin@lists.postgresql.org; Tue, 22 Aug 2023 12:03:49 +0000 Received: from cc-smtpout2.netcologne.de ([2001:4dd0:100:1062:25:2:0:2]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYQ6r-000MZn-EP for pgsql-admin@lists.postgresql.org; Tue, 22 Aug 2023 12:03:48 +0000 Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout2.netcologne.de (Postfix) with ESMTP id 561CE126D3 for ; Tue, 22 Aug 2023 14:03:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1692705823; bh=/wrL/wup66gZA+WA60C50c5q+1EYTA9pO0pli0icYL4=; h=Message-ID:Date:Subject:References:To:From:In-Reply-To:From; b=NI0M2imeiqeUYlNgk7Xh5OdnpOEgJc7gjvJsgFupyQKDV/t1nIHLldZcmj8MmLzIr ZRw5zH6uX7XjDRpbKcQhCuFgrBawxcjl15ShPoWECzeMlVXzZgJ9opJjZOxCzA88Aw wwB8jxV6nexF//e2Dbkv+1wHH22FeyxAxPDDL8cEDBfO/thUVor6Aokn7qFEjhDzF+ f8pUTkxGWusOcU/opQ5MxMbndr0tIwYRUmkiduv/FHYEfc3VKjzhYpU0DI6VHByuJP wHUxm9mHES0cpEfyxDGmuDZjBQY21NKpcIKzUemBgiBXvrJMW3phGxdosMAx6k4EKM iNk0iQl5hgT4g== Received: from [IPV6:2003:ce:df04:9100:d90:6746:f430:56d3] (p200300cedf0491000d906746f43056d3.dip0.t-ipconnect.de [IPv6:2003:ce:df04:9100:d90:6746:f430:56d3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA id 2D273120DB for ; Tue, 22 Aug 2023 14:03:42 +0200 (CEST) Content-Type: multipart/alternative; boundary="------------LsaVG01oXxFSByPiCwuy0PTU" Message-ID: <0242964f-7cc2-4172-81ca-e05a7f8ee613@netcologne.de> Date: Tue, 22 Aug 2023 14:03:42 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Compatibility postgis Content-Language: en-US References: To: pgsql-admin@lists.postgresql.org From: vrms In-Reply-To: X-Forwarded-Message-Id: X-NetCologne-Spam: L X-Rspamd-Action: no action X-Rspamd-Queue-Id: 2D273120DB X-Spamd-Bar: - List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------LsaVG01oXxFSByPiCwuy0PTU Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit compatibility between postgres/GIS as well as upgrading is a little tricky. This is a good starting point to see what you have to aim for. Next challenge is to figure out a workable upgrade path as it is not unlikely you will have to go through some intermediate steps. Maybe it would help whether you can specify which PostGIS version you are coming from on the source (postgres-12) Installation. On 22.08.23 09:35, Rajesh Kumar wrote: > I am tring to upgrade from postgres 12 to postgres 15. > > And it seems like posigis extension I have on V12 is not compatible > with V15. > > I get following error > > > command: "/usr/pgsql-15/bin/pg_dump" --host /var/lib/pgsql --port > 50432 --username postgres --schema-only --quote-all-identifiers > --binary-upgrade --format=cu stom > --file="/var/lib/pgsql/data/15/data/pg_upgrade_output.d/20230818T082920.083/dump/pg_upgrade_dump_27286.custom" > 'dbname=common' >> "/var/lib/pgsql/data/1 > 5/data/pg_upgrade_output.d/20230818T082920.083/log/pg_upgrade_dump_27286.log" > 2>&1 pg_dump: error: query failed: ERROR: could not access file > "$libdir/postgis-3": No such file or directory > --------------LsaVG01oXxFSByPiCwuy0PTU Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
compatibility between postgres/GIS as well as upgrading is a little tricky.
This is a good starting point to see what you have to aim for.

Next challenge is to figure out a workable upgrade path as it is not unlikely you will have to go through some intermediate steps.

Maybe it would help whether you can specify which PostGIS version you are coming from on the source (postgres-12) Installation.

On 22.08.23 09:35, Rajesh Kumar wrote:
I am tring to upgrade from postgres 12 to postgres 15.

And it seems like posigis extension I have on V12 is not compatible with V15.

I get following error


command: "/usr/pgsql-15/bin/pg_dump" --host /var/lib/pgsql --port 50432 --username postgres --schema-only --quote-all-identifiers --binary-upgrade --format=cu stom --file="/var/lib/pgsql/data/15/data/pg_upgrade_output.d/20230818T082920.083/dump/pg_upgrade_dump_27286.custom" 'dbname=common' >> "/var/lib/pgsql/data/1 5/data/pg_upgrade_output.d/20230818T082920.083/log/pg_upgrade_dump_27286.log" 2>&1 pg_dump: error: query failed: ERROR: could not access file "$libdir/postgis-3": No such file or directory

--------------LsaVG01oXxFSByPiCwuy0PTU--