# Cleanup some files/paths that should not be in the backup. There is no # attempt to handle all the exclusions done by pg_basebackup here, in part # because these are not required, but also to keep the test simple. # # Also remove pg_control because it needs to be copied later.
unlink("$backup_dir/postmaster.pid")
or BAIL_OUT("unable to unlink $backup_dir/postmaster.pid");
unlink("$backup_dir/postmaster.opts")
or BAIL_OUT("unable to unlink $backup_dir/postmaster.opts");
unlink("$backup_dir/global/pg_control")
or BAIL_OUT("unable to unlink $backup_dir/global/pg_control");
rmtree("$backup_dir/pg_wal")
or BAIL_OUT("unable to unlink contents of $backup_dir/pg_wal");
mkdir("$backup_dir/pg_wal");
# Create a table that will be used to verify that recovery started at the # correct location, rather than a location recorded in the control file.
$node_primary->safe_psql('postgres', "create table canary (id int)");
# Advance the checkpoint location in pg_control past the location where the # backup started. Switch WAL to make it really clear that the location is # different and to put the checkpoint in a new WAL segment.
my $segment_name = $node_primary->safe_psql('postgres', "select pg_walfile_name(pg_switch_wal())");
# Ensure that the segment just switched from is archived. The follow-up # tests depend on its presence to begin recovery.
$node_primary->poll_query_until('postgres',
q{SELECT last_archived_wal FROM pg_stat_archiver},
$segment_name)
or die "Timed out while waiting for archiving of switched segment to finish";
# Copy pg_control last so it contains the new checkpoint. copy($node_primary->data_dir . '/global/pg_control', "$backup_dir/global/pg_control")
or BAIL_OUT("unable to copy global/pg_control");
# Save the name segment that will be archived by pg_backup_stop(). # This is copied to the pg_wal directory of the node whose recovery # is done without a backup_label.
my $stop_segment_name = $node_primary->safe_psql('postgres', 'SELECT pg_walfile_name(pg_current_wal_lsn())');
# Stop backup and get backup_label, the last segment is archived.
my $backup_label =
$psql->query_safe("select labelfile from pg_backup_stop()");
$psql->quit;
# Rather than writing out backup_label, try to recover the backup without # backup_label to demonstrate that recovery will not work correctly without it, # i.e. the canary table will be missing and the cluster will be corrupted. # Provide only the WAL segment that recovery will think it needs. # # The point of this test is to explicitly demonstrate that backup_label is # being used in a later test to get the correct recovery info.
my $node_replica = PostgreSQL::Test::Cluster->new('replica_fail');
$node_replica->init_from_backup($node_primary, $backup_name);
$node_replica->append_conf('postgresql.conf', "archive_mode = off");
my $canary_query = "select count(*) from pg_class where relname = 'canary'";
copy(
$node_primary->archive_dir . "/$stop_segment_name",
$node_replica->data_dir . "/pg_wal/$stop_segment_name"
) or BAIL_OUT("unable to copy $stop_segment_name");
$node_replica->start;
is($node_replica->safe_psql('postgres', $canary_query), '0', 'canary is missing');
# Check log to ensure that crash recovery was used as there is no # backup_label.
ok( $node_replica->log_contains( 'database system was not properly shut down; automatic recovery in progress'
), 'verify backup recovery performed with crash recovery');
# Save backup_label into the backup directory and recover using the primary's # archive. This time recovery will succeed and the canary table will be # present.
open my $fh, ">>", "$backup_dir/backup_label"
or die "could not open backup_label"; # Binary mode is required for Windows, as the backup_label parsing is not # able to cope with CRLFs.
binmode $fh;
print $fh $backup_label;
close $fh;
is($node_replica->safe_psql('postgres', $canary_query), '1', 'canary is present');
# Check log to ensure that backup_label was used for recovery.
ok($node_replica->log_contains('starting backup recovery with redo LSN'), 'verify backup recovery performed with backup_label');
done_testing();
Messung V0.5 in Prozent
¤ Dauer der Verarbeitung: 0.11 Sekunden
(vorverarbeitet am 2026-08-10)
¤
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.