| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixing WAL instability in various TAP tests |
| Date: | 2021-09-27 22:49:31 |
| Message-ID: | 2790908.1632782971@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> writes:
>> On Sep 27, 2021, at 1:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm a little inclined to re-enable the test without your other
>> changes, just to see what happens.
> That sounds like a good idea. Even if it passes at first, I'd prefer to leave it for a week or more to have a better sense of how stable it is. Applying my patches too soon would just add more variables to a not-so-well understood situation.
Done. I shall retire to a safe viewing distance and observe the
buildfarm.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rachel Heaton | 2021-09-27 22:55:02 | [PATCH] Print error when libpq-refs-stamp fails |
| Previous Message | Tom Lane | 2021-09-27 21:54:46 | Couldn't we mark enum_in() as immutable? |