| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: A test for replay of regression tests |
| Date: | 2021-05-04 11:12:17 |
| Message-ID: | CA+hUKGKV=41jk78E_tcHp4m3ab77_gPgbLuE4=WADbmEj4ETTA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ok, here's a new version incorporating feedback so far.
1. Invoke pg_regress directly (no make).
2. Use PG_TEST_EXTRA="wal_consistency_checking" as a way to opt in to
the more expensive test.
3. Use parallel schedule rather than serial. It's faster but also
the non-determinism might discover more things. This required
changing the TAP test max_connections setting from 10 to 25.
4. Remove some extraneous print statements and
check-if-data-is-replicated-using-SELECT tests that are technically
not needed (I had copied those from 001_stream_rep.pl).
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Test-replay-of-regression-tests.patch | text/x-patch | 7.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2021-05-04 12:11:06 | Re: Race condition in recovery? |
| Previous Message | Peter Eisentraut | 2021-05-04 10:27:03 | Re: Dumping/restoring fails on inherited generated column |