Re: Occasional tablespace.sql failures in check-world -jnn

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Occasional tablespace.sql failures in check-world -jnn
Date: 2021-03-08 10:53:57
Message-ID: dd821b71-bfae-a119-5007-fd702ce0d646@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09.12.20 08:55, Michael Paquier wrote:
>> It's not clear to me why we have this logic in the makefile at all?
>> Somebody taught pg_regress to do so, but only on windows... See
>> convert_sourcefiles_in().
>
> ... Because we may still introduce this problem again if some new
> stuff uses src/test/pg_regress in a way similar to pg_upgrade,
> triggering again tablespace-setup. Something like the attached may be
> enough, though I have not spent much time checking the surroundings,
> Windows included.

This patch looks alright to me.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tharakan, Robins 2021-03-08 11:00:43 RE: pg_upgrade failing for 200+ million Large Objects
Previous Message Fabien COELHO 2021-03-08 10:50:43 Re: pgbench - add pseudo-random permutation function