On Thu, 21 Nov 2024 at 14:19, Tomas Vondra <tomas@vondra.me> wrote:
On 11/21/24 15:03, Daniel Gustafsson wrote: >> On Thu, 21 Nov 2024, 17:46 Daniel Gustafsson, <daniel@yesql.se> wrote: >>> On 21 Nov 2024, at 04:22, Sanjay Khatri <sanjaykhatri218@gmail.com> wrote: >>> >>> We tried it on another server with similar configurations. >>> Just installed the Postgres 15 and its PgAdmin. >>> Kept the server ONN for the whole day, the server was okay. >>> But then we tried the pgAdmin workaround by deleting the pgAdmin.bak file in 'AppData/Roaming/pgAdmin' and restarted the PgAdmin. >>> Soon within an hour the server crashed. Its happening when PgAdmin workaround is performed. >>> Do Let me know if someone else faced the same issue? >> >> Just to make sure we're talking about the same thing. Did Windows crash and >> required a restart when you removed a file from pgAdmin, or did the server get >> bricked and refused to boot at all with systems diagnostics issues? >> >> On 21 Nov 2024, at 14:50, Sanjay Khatri <sanjaykhatri218@gmail.com> wrote: >> >> Yes we are talking about same thing. >> But this time a different server with Similar configuration. >> On deleting the pgAdmin.bak file after which I restarted pgAdmin. But after an hour or two, the machine crashed and refuses to boot. > > If removing a file from pgAdmin can brick your server (regardless of it being > standard operating procedure or not), then I think it's something which the > pgAdmin developers should be made aware of. >
Color me skeptical. Weird unexpected things happen, but I simply don't see how removing a .bak file from a regular application, could break the BIOS and cause machine check exceptions there. These things are at least two or three steps apart (BIOS <-> OS <-> application).
Speaking as a pgAdmin dev, and someone with a fair amount of Windows experience over the years, I'd say there is approximately zero chance that deleting a file from a user's roaming profile directory would brick a server, especially a backup of the pgAdmin configuration database (which is a SQLite file).
For those that don't know, the roaming profile directory on Windows is a directory where a user's config/data files get synchronised onto each machine they log into within the domain. The equivalent on Linux/macOS is a file in ~/.pgadmin4/ or something along those lines. It is absolutely not a critical part of the OS.
It's far more likely this is just a traditional hardware issue. If you search for "dell machine check error" you'll find plenty of similar reports. I only checked a couple, but it's invariably some due to some hardware issue.
