Re: src/test/regress/standby_schedule

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: src/test/regress/standby_schedule
Date: 2020-04-03 00:29:19
Message-ID: 13680.1585873759@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> I guess no human or machine ever runs $SUBJECT, because when I tried
> it while hunting down users of txid_XXX functions, it failed (see
> end). To run it, you need a primary/standby pair, here 5441/5442, and
> then:

> PGPORT=5441 psql postgres -f sql/hs_primary_setup.sql
> PGPORT=5442 ./pg_regress --use-existing --dbname=postgres --schedule
> standby_schedule

> Perhaps the output changed in January with commit 2eb34ac3. Easy to
> fix, but I wonder if anyone has a good idea for how to get check-world
> to run it (probably via the "recovery" stuff).

That stuff is very very ancient. I'd suggest nuking it and writing
an equivalent TAP test, assuming that there's anything it does that's
not already covered by our existing TAP tests.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2020-04-03 00:46:30 Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Previous Message Thomas Munro 2020-04-03 00:24:10 src/test/regress/standby_schedule