| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_resetwal tests, logging, and docs update |
| Date: | 2023-08-30 12:45:30 |
| Message-ID: | 0f3ab4a1-ae80-56e8-3426-6b4a02507687@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I noticed that pg_resetwal has poor test coverage. There are some TAP
tests, but they all run with -n, so they don't actually test the full
functionality. (There is a non-dry-run call of pg_resetwal in the
recovery test suite, but that is incidental.)
So I added a bunch of more tests to test all the different options and
scenarios. That also led to adding more documentation about more
details how some of the options behave, and some tweaks in the program
output.
It's attached as one big patch, but it could be split into smaller
pieces, depending what gets agreement.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-pg_resetwal-More-tests-and-some-output-improvemen.patch | text/plain | 18.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-08-30 12:49:45 | Re: Commitfest manager for September |
| Previous Message | Jim Jones | 2023-08-30 12:38:52 | Re: PATCH: Add REINDEX tag to event triggers |