]> granicus.if.org Git - postgresql/commit
Add more tests for commit_timestamp feature
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 1 Mar 2016 22:53:18 +0000 (19:53 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 1 Mar 2016 22:53:18 +0000 (19:53 -0300)
commit9def031bd2821f35b5f506260d922482648a8bb0
treeec5a489d9f13c36448540c0b733d8261335aed9a
parent88802e068017bee8cea7a5502a712794e761c7b5
Add more tests for commit_timestamp feature

These tests verify that 1) WAL replay preserves the stored value,
2) a streaming standby server replays the value obtained from the
master, and 3) the behavior is sensible in the face of repeated
configuration changes.

One annoyance is that tmp_check/ subdir from the TAP tests is clobbered
when the pg_regress test runs in the same subdirectory.  This is
bothersome but not too terrible a problem, since the pg_regress test is
not run anyway if the TAP tests fail (unless "make -k" is used).

I had these tests around since commit 69e7235c93e2; add them now that we
have the recovery test framework in place.
src/test/modules/commit_ts/Makefile
src/test/modules/commit_ts/t/001_base.pl [new file with mode: 0644]
src/test/modules/commit_ts/t/002_standby.pl [new file with mode: 0644]
src/test/modules/commit_ts/t/003_standby_2.pl [new file with mode: 0644]