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 1qYXDp-0020dL-WB for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2023 19:39:27 +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 1qYXDo-004ZYC-I2 for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2023 19:39:24 +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 1qYPdR-000C5B-4i for pgsql-admin@lists.postgresql.org; Tue, 22 Aug 2023 11:33:21 +0000 Received: from mout-p-103.mailbox.org ([80.241.56.161]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYPdN-000MLz-2l for pgsql-admin@lists.postgresql.org; Tue, 22 Aug 2023 11:33:19 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4RVRzq2wDWz9sSP for ; Tue, 22 Aug 2023 13:33:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1692703991; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3KBpNsn/AcRFZbwWjKxIWzgd6/L46cIissQndfsao4Y=; b=mgIqj4qm4/9xqPcEwsIhsnu67rUdA7+AsRE+smhdcgVL91BoZH6yg44KPx++EspRSkwISh tR+M3HQie8fRe/n1Ckp5Q9hoS75oMPND5FpDfdNzuf0tzYWFB0Pa4/MSuP2Am0rtKvo95/ 7TYSNqBGi0auGpoqYFqwA/B6+Z70KbT+ICotiX6+6vRBFBTgg6wULycJNuoGhdCTz9TRsG g85BxLrjbL0QaDCETlrhpcsdhFLGjPfPo0wVgnWKZZewnRyNSw04jWNQN0tQN+iqr0F5UU IXvILcUA+wSI4MD8uOH7PIFp2dU13JGtmIPsV40LIUKrrbel38rHASo6d+tIQQ== Content-Type: multipart/alternative; boundary="------------Ux3MCmyzgzhEy6fpkKDcj0Ak" Message-ID: Date: Tue, 22 Aug 2023 13:33:09 +0200 MIME-Version: 1.0 Subject: Re: Compatibility postgis To: pgsql-admin@lists.postgresql.org References: Content-Language: en-US From: dulhaver@mailbox.org In-Reply-To: X-MBO-RS-ID: 6e79f78ba2924382cdb X-MBO-RS-META: amp7xfxipky56bu7orafm6ecscgxyjsx 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. --------------Ux3MCmyzgzhEy6fpkKDcj0Ak Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit compatibility between postgres/GIS 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 > --------------Ux3MCmyzgzhEy6fpkKDcj0Ak Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit compatibility between postgres/GIS 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

--------------Ux3MCmyzgzhEy6fpkKDcj0Ak--