Re: Test 002_pg_upgrade fails with olddump on Windows

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Test 002_pg_upgrade fails with olddump on Windows
Date: 2023-12-08 10:51:53
Message-ID: 202312081051.fg4cnf7klxx6@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2023-Dec-08, Michael Paquier wrote:

> On Thu, Dec 07, 2023 at 05:44:53PM +0900, Michael Paquier wrote:
> > Hmm. Yes, it looks like you're right here. That should allow all the
> > scenarios we expect to work to update the paths for the functions.
> And done this one as well down to v15, where not only meson, but also
> vpath could have been confused with an update to an incorrect path.

Argh, yeah, this has caused me pain a couple of times. Thanks for fixing.

Álvaro Herrera 48°01'N 7°57'E —
"If you have nothing to say, maybe you need just the right tool to help you
not say it." (New York Times, about Microsoft PowerPoint)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shubham Khanna 2023-12-08 11:06:58 Re: Adding a pg_get_owned_sequence function?
Previous Message John Naylor 2023-12-08 10:46:29 Re: [PoC] Improve dead tuple storage for lazy vacuum