Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
От | Daniel Gustafsson |
---|---|
Тема | Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin |
Дата | |
Msg-id | BE29D68F-3565-48BA-A289-8B859D47AC69@yesql.se обсуждение исходный текст |
Ответ на | Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin (Sanjay Khatri <sanjaykhatri218@gmail.com>) |
Ответы |
Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin
|
Список | pgsql-hackers |
> 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 restartedthe 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 refusesto 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. -- Daniel Gustafsson
В списке pgsql-hackers по дате отправления: