Re: BUG #19392: PG_UPGRADE is non-functional on Windows - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: BUG #19392: PG_UPGRADE is non-functional on Windows
Date
Msg-id e55df878-bcb0-4b2e-b413-49c57beb20fe@dunslane.net
Whole thread Raw
In response to Re: BUG #19392: PG_UPGRADE is non-functional on Windows  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs


On 2026-02-04 We 1:43 AM, David G. Johnston wrote:
On Tuesday, February 3, 2026, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      19392
Logged by:          Jeff Laing
Email address:      jeff.laing@spatialnetworx.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

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #19392: PG_UPGRADE is non-functional on Windows
Next
From: PG Bug reporting form
Date:
Subject: BUG #19393: pg_upgrade fails with duplicate key violation when CHECK constraint named *_not_null exists