Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
Date
Msg-id CAEudQApD1a-hRFNF-Ruk6e_QJMSohyhk7ZoqPEFSuznwrrt2cg@mail.gmail.com
Whole thread Raw
In response to Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin  (Sanjay Khatri <sanjaykhatri218@gmail.com>)
List pgsql-hackers
Hi.

Em qui., 21 de nov. de 2024 às 12:46, Sanjay Khatri <sanjaykhatri218@gmail.com> escreveu:

Yes...I have myself installed pgAmdin more than 50 times so far. But this, for the first time ever I have faced this issue. Just try deleting the pgAdmin.bak file for the pg15.8 on a Windows server 2016.
Try doing that, lets see.

On Thu, 21 Nov 2024, 21:13 Dave Page, <dpage@pgadmin.org> wrote:


On Thu, 21 Nov 2024 at 15:35, Sanjay Khatri <sanjaykhatri218@gmail.com> wrote:

I know its hard to believe this. But you can try doing this from your side and respond here back again.


I can't speak for Robert, but I've installed and run pgAdmin literally hundreds of times on Windows, Mac, and Linux, and have never seen it even crash a whole machine, let alone render one unbootable. We also probably have hundreds of thousands of users on Windows (based on the number of downloads we get), and have never had such a problem reported.
I agree with Dave Page.
There is a zero chance that Postgres or pgAdmin, may crash or damage the Windows Server.
None of these has kernel access.

You should be careful about:
Old antivirus software
Kernel storage incompative drivers
Third-party drivers
Hardware failure

best regards,
Ranier Vilela

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Document NULL
Next
From: Nathan Bossart
Date:
Subject: Re: SQL:2011 application time