| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-21 15:19:20 |
| Message-ID: | CA+TgmoaoQaV0bb-r2GTCW0cZ2BHeEioVyTbwA4zfS5045t=NxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 21, 2024 at 9:53 AM Dave Page <dpage(at)pgadmin(dot)org> wrote:
> 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).
I know a lot less about Windows than you do, but I'm sure you're
correct, especially because the crash happened "an hour or two" after
deleting pgAdmin.bak.
This whole discussion seems quite silly to me.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sanjay Khatri | 2024-11-21 15:35:05 | Re: Windows 2016 server crashed after changes in Postgres 15.8 pgAdmin |
| Previous Message | Robert Haas | 2024-11-21 15:09:35 | Re: Accessing other session's temp table |