Re: BUG #16484: pg_regress fails with --outputdir parameter

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, r(dot)zharkov(at)postgrespro(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16484: pg_regress fails with --outputdir parameter
Date: 2020-06-11 09:59:20
Message-ID: A6F25BFE-D40B-4B02-B8FB-F148193F3549@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 11 Jun 2020, at 10:27, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> I have left this path creation intentionally actually because there is a patch
> to improve this area in the works and we have to check this area of the code so
> leaving it behind makes grepping for testtablespace harder to forget

Aha, I hadn't seen that patch, but I agree it makes sense to leave it for now
then. +1 on the attached.

cheers ./daniel

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2020-06-11 10:12:47 Re: Potential G2-item cycles under serializable isolation
Previous Message Andrei Zhidenkov 2020-06-11 09:04:30 Re: pg_cancel_backend() doesn't abort a transaction