| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "jeff(dot)laing(at)spatialnetworx(dot)ai" <jeff(dot)laing(at)spatialnetworx(dot)ai>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #19392: PG_UPGRADE is non-functional on Windows |
| Date: | 2026-02-04 12:32:34 |
| Message-ID: | e55df878-bcb0-4b2e-b413-49c57beb20fe@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2026-02-04 We 1:43 AM, David G. Johnston wrote:
> On Tuesday, February 3, 2026, PG Bug reporting form
> <noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 19392
> Logged by: Jeff Laing
> Email address: jeff(dot)laing(at)spatialnetworx(dot)ai
> PostgreSQL version: 18.1
> Operating system: Windows 11
> Description:
>
> After struggling with it for a while, I’ve come to the conclusion that
> PG_UPGRADE is not functional on Windows.
>
>
> This is a very hard to accept premise and this bug report doesn’t
> support it.
>
>
pg_upgrade is tested on Windows all the time, both in the buildfarm and
in CI, so the statement that it is not functional doesn't add up.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-02-04 17:33:21 | BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists |
| Previous Message | Michael Paquier | 2026-02-04 06:50:09 | Re: BUG #19392: PG_UPGRADE is non-functional on Windows |