| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Sanjay Khatri <sanjaykhatri218(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, 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 12:16:04 |
| Message-ID: | 31E4BAF9-0BA5-4C0D-973F-2C4B2851C5F6@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 21 Nov 2024, at 04:22, Sanjay Khatri <sanjaykhatri218(at)gmail(dot)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?
Also, I assume these machines are sitting behind ample firewall protection to
keep outside bad actors from reaching them?
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2024-11-21 12:35:49 | Re: 039_end_of_wal: error in "xl_tot_len zero" test |
| Previous Message | Nisha Moond | 2024-11-21 12:05:01 | Re: Introduce XID age and inactive timeout based replication slot invalidation |