Re: src/test/regress/standby_schedule - Mailing list pgsql-hackers

From Tom Lane
Subject Re: src/test/regress/standby_schedule
Date
Msg-id 13680.1585873759@sss.pgh.pa.us
Whole thread Raw
In response to src/test/regress/standby_schedule  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.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



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: src/test/regress/standby_schedule
Next
From: James Coleman
Date:
Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort)