aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/commit_ts/t/002_standby.pl
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2016-03-01 19:53:18 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2016-03-01 19:53:18 -0300
commit9def031bd2821f35b5f506260d922482648a8bb0 (patch)
treeec5a489d9f13c36448540c0b733d8261335aed9a /src/test/modules/commit_ts/t/002_standby.pl
parent88802e068017bee8cea7a5502a712794e761c7b5 (diff)
downloadpostgresql-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/t/002_standby.pl')
-rw-r--r--src/test/modules/commit_ts/t/002_standby.pl55
1 files changed, 55 insertions, 0 deletions
diff --git a/src/test/modules/commit_ts/t/002_standby.pl b/src/test/modules/commit_ts/t/002_standby.pl
new file mode 100644
index 00000000000..5cc2501c36c
--- /dev/null
+++ b/src/test/modules/commit_ts/t/002_standby.pl
@@ -0,0 +1,55 @@
+# Test simple scenario involving a standby
+
+use strict;
+use warnings;
+
+use TestLib;
+use Test::More tests => 2;
+use PostgresNode;
+
+my $bkplabel = 'backup';
+my $master = get_new_node('master');
+$master->init(allows_streaming => 1);
+
+$master->append_conf('postgresql.conf', qq{
+ track_commit_timestamp = on
+ max_wal_senders = 5
+ wal_level = hot_standby
+ });
+$master->start;
+$master->backup($bkplabel);
+
+my $standby = get_new_node('standby');
+$standby->init_from_backup($master, $bkplabel, has_streaming => 1);
+$standby->start;
+
+for my $i (1 .. 10)
+{
+ $master->psql('postgres', "create table t$i()");
+}
+my $master_ts = $master->psql('postgres',
+ qq{SELECT ts.* FROM pg_class, pg_xact_commit_timestamp(xmin) AS ts WHERE relname = 't10'});
+my $master_lsn = $master->psql('postgres',
+ 'select pg_current_xlog_location()');
+$standby->poll_query_until('postgres',
+ qq{SELECT '$master_lsn'::pg_lsn <= pg_last_xlog_replay_location()})
+ or die "slave never caught up";
+
+my $standby_ts = $standby->psql('postgres',
+ qq{select ts.* from pg_class, pg_xact_commit_timestamp(xmin) ts where relname = 't10'});
+is($master_ts, $standby_ts, "standby gives same value as master");
+
+$master->append_conf('postgresql.conf', 'track_commit_timestamp = off');
+$master->restart;
+$master->psql('postgres', 'checkpoint');
+$master_lsn = $master->psql('postgres',
+ 'select pg_current_xlog_location()');
+$standby->poll_query_until('postgres',
+ qq{SELECT '$master_lsn'::pg_lsn <= pg_last_xlog_replay_location()})
+ or die "slave never caught up";
+$standby->psql('postgres', 'checkpoint');
+
+# This one should raise an error now
+$standby_ts = $standby->psql('postgres',
+ 'select ts.* from pg_class, pg_xact_commit_timestamp(xmin) ts where relname = \'t10\'');
+is($standby_ts, '', "standby gives no value when master turned feature off");