From: | Sanjay Khatri <sanjaykhatri218(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin |
Date: | 2024-11-21 15:46:07 |
Message-ID: | CANLv43KmuHmQX-mfVS6K_Jg6X_KvWHoe7rkBeRnf9Ka8SxiAKA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)pgadmin(dot)org> wrote:
>
>
> On Thu, 21 Nov 2024 at 15:35, Sanjay Khatri <sanjaykhatri218(at)gmail(dot)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.
>
> --
> Dave Page
> pgAdmin: https://www.pgadmin.org
> PostgreSQL: https://www.postgresql.org
> pgEdge: https://www.pgedge.com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey M. Borodin | 2024-11-21 15:57:32 | Re: Accessing other session's temp table |
Previous Message | Dave Page | 2024-11-21 15:42:58 | Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin |