Re: [PATCH] hs_standby_disallowed test fix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] hs_standby_disallowed test fix
Date: 2020-05-12 17:35:53
Message-ID: 29730.1589304953@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> writes:
> I just wonder why standbycheck regression test doesn't run by default
> in buildfarm. Which caused us not to notice this issue long time. Maybe
> because it's difficult to set up hot-standby environment in the
> regression test? If so, we might need to merge standbycheck test into
> TAP tests for recovery.

It seems likely to me that the standbycheck stuff has been completely
obsoleted by the TAP-based recovery tests. We should get rid of it,
after adding any missing coverage to the TAP tests.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-05-12 17:47:38 Re: PG 13 release notes, first draft
Previous Message Tom Lane 2020-05-12 17:10:08 Re: gcov coverage data not full with immediate stop