Re: Finding cause of test fails on the cfbot site

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Finding cause of test fails on the cfbot site
Date: 2021-02-22 02:28:27
Message-ID: CA+hUKG+-6F6aZZaiZ-uQ48b5mm3EAEYk79u_s6XSvWzBmn8sPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 20, 2021 at 3:54 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> here's a very small and simple (and possibly naive) POC patch that
> demonstrates this and seems to do the right thing.

As a small variation that might be more parallelism-friendly, would it
be better to touch a file with a known name in any subdirectory that
contains potentially interesting logs, and rm it when a test succeeds?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-02-22 02:52:35 Re: repeated decoding of prepared transactions
Previous Message Andres Freund 2021-02-22 02:24:07 Re: Catalog version access