diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2016-03-01 19:53:18 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2016-03-01 19:53:18 -0300 |
| commit | 9def031bd2821f35b5f506260d922482648a8bb0 (patch) | |
| tree | ec5a489d9f13c36448540c0b733d8261335aed9a /src/test/modules/commit_ts/sql | |
| parent | 88802e068017bee8cea7a5502a712794e761c7b5 (diff) | |
| download | postgresql-9def031bd2821f35b5f506260d922482648a8bb0.tar.gz postgresql-9def031bd2821f35b5f506260d922482648a8bb0.zip | |
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.
Diffstat (limited to 'src/test/modules/commit_ts/sql')
0 files changed, 0 insertions, 0 deletions