Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12. - Mailing list pgsql-bugs

From Zaid Shabbir
Subject Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12.
Date
Msg-id CABCJe_VNN2yhKXvfXPq1M7hM8N3skiDZ=Kury+hxGuB8yPwtBQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18726: Unable to install PostGIS extension due to error:Checksum verification failed for: postgis_3_4_pg12.  (Erik Wienhold <ewie@ewie.name>)
List pgsql-bugs
Hello,

Please clear your browser cache and try again, sometimes these types of issues occur due to wrong cache entries. Secondly don't forget to upgrade your server 12 because it's going to EOL. 

Regards,
Zaid

On Wed, Nov 27, 2024 at 10:54 PM Erik Wienhold <ewie@ewie.name> wrote:
On 2024-11-27 17:34 +0100, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference:      18726
> Logged by:          Swaminathan Sivakumar
> Email address:      reply2swami@gmail.com
> PostgreSQL version: Unsupported/Unknown
> Operating system:   Windows
> Description:       
>
> I am trying to install the PostGIS extension using the PostGIS 3.4 Bundle
> for PostgreSQL 12  (64 bit) v3.4.2

Please note that Postgres 12 just reached end-of-life with the release
of 12.22.  You should upgrade soon.

> But I am unable to install PostGIS extension in my local Postgres version
> 12.
> I am getting the error : Checksum verification failed for:
> postgis_3_4_pg12.exe! Deleting file.....

This looks like some antivirus scanner or other malware protection is
kicking in.  Where did you get postgis_3_4_pg12.exe from?  The official
Windows releases on [1] use different filenames.

[1] https://download.osgeo.org/postgis/windows/pg12/

--
Erik


pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Next
From: Tom Lane
Date:
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails