Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Sanjay Khatri <sanjaykhatri218(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
Date: 2024-11-20 12:56:27
Message-ID: 325AB9CB-CA22-4B7E-AFE9-8B8062FE0252@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Nov 2024, at 13:36, Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> On 11/19/24 17:44, Sanjay Khatri wrote:

>> And we dont have any data backup too.

This will be your first priority once the system is up and running again, maybe
even to the point of planning for what immediate action to take before the
system boots to be able to act quickly in case it falls over again.

> It's very unlikely a Postgres issue would make the whole system crash,
> particularly in a way that prevents it from booting again.

Agreed, especially since this crash reportedly happened after uninstalling
postgres. If the uninstaller could corrupt the OS like that I have a feeling
we'd heard about it by now.

> I don't think
> anyone will be able to help you without more info - you need to make it
> boot again, inspect the Postgres logs, etc.

I'm not familiar with Dell blade enclosures but if there is a similar system to
the iLO Lights Out console that HP ships I would start there (a quick Google
search hints at ePSA).

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-11-20 12:58:11 Re: cannot freeze committed xmax
Previous Message Justin Pryzby 2024-11-20 12:43:58 Re: ALTER TABLE uses a bistate but not for toast tables