Results.log

application/octet-stream

Download

==================== TEST CASE 1 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" -d db2 --publication pub_new2 --clean=publications --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:48.245 IST [1778730] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:48.249 IST [1778730] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:48.260 IST [1778736] LOG:  database system was shut down in recovery at 2025-10-10 11:50:48 IST
2025-10-10 11:50:48.261 IST [1778736] LOG:  entering standby mode
2025-10-10 11:50:48.266 IST [1778736] LOG:  redo starts at 0/03000028
2025-10-10 11:50:48.266 IST [1778736] LOG:  consistent recovery state reached at 0/04000000
2025-10-10 11:50:48.266 IST [1778730] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:48.272 IST [1778737] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:48.387 IST [1778730] LOG:  received fast shutdown request
2025-10-10 11:50:48.391 IST [1778730] LOG:  aborting any active transactions
2025-10-10 11:50:48.392 IST [1778737] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:48.396 IST [1778734] LOG:  shutting down
2025-10-10 11:50:48.410 IST [1778730] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pub_new2" in database "db2"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16386_9dfc0b4b" in database "db2" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:48.531 IST [1778749] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:48.533 IST [1778749] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:48.545 IST [1778755] LOG:  database system was shut down in recovery at 2025-10-10 11:50:48 IST
2025-10-10 11:50:48.545 IST [1778755] LOG:  entering standby mode
2025-10-10 11:50:48.548 IST [1778755] LOG:  redo starts at 0/03000028
2025-10-10 11:50:48.548 IST [1778755] LOG:  consistent recovery state reached at 0/04000000
2025-10-10 11:50:48.548 IST [1778749] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:48.556 IST [1778756] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping all existing publications in database "db2"
pg_createsubscriber: dropping publication "pub_exists1" in database "db2"
pg_createsubscriber: dropping publication "pub_exists2" in database "db2"
pg_createsubscriber: dropping publication "pub_exists3" in database "db2"
pg_createsubscriber: dropping publication "pub_exists4" in database "db2"
pg_createsubscriber: dropping publication "pub_new2" in database "db2"
pg_createsubscriber: creating subscription "pg_createsubscriber_16386_9dfc0b4b" in database "db2"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "db2"
pg_createsubscriber: enabling subscription "pg_createsubscriber_16386_9dfc0b4b" in database "db2"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:48.685 IST [1778749] LOG:  received fast shutdown request
2025-10-10 11:50:48.709 IST [1778749] LOG:  aborting any active transactions
2025-10-10 11:50:48.734 IST [1778756] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:48.736 IST [1778753] LOG:  shutting down
2025-10-10 11:50:48.749 IST [1778749] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474221815452704 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

==================== TEST CASE 2 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" -d db2 --publication pub_new2 --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:48.842 IST [1778777] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:48.846 IST [1778777] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:48.856 IST [1778783] LOG:  database system was shut down in recovery at 2025-10-10 11:50:48 IST
2025-10-10 11:50:48.858 IST [1778783] LOG:  entering standby mode
2025-10-10 11:50:48.863 IST [1778783] LOG:  redo starts at 0/03000028
2025-10-10 11:50:48.863 IST [1778783] LOG:  consistent recovery state reached at 0/04000000
2025-10-10 11:50:48.863 IST [1778783] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-10 11:50:48.863 IST [1778777] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:48.869 IST [1778784] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:48.987 IST [1778777] LOG:  received fast shutdown request
2025-10-10 11:50:48.990 IST [1778777] LOG:  aborting any active transactions
2025-10-10 11:50:48.990 IST [1778784] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:48.997 IST [1778781] LOG:  shutting down
2025-10-10 11:50:49.009 IST [1778777] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pub_new2" in database "db2"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16386_46bc8ee7" in database "db2" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:49.132 IST [1778796] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:49.134 IST [1778796] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:49.145 IST [1778802] LOG:  database system was shut down in recovery at 2025-10-10 11:50:48 IST
2025-10-10 11:50:49.147 IST [1778802] LOG:  entering standby mode
2025-10-10 11:50:49.151 IST [1778802] LOG:  redo starts at 0/03000028
2025-10-10 11:50:49.151 IST [1778802] LOG:  consistent recovery state reached at 0/04000228
2025-10-10 11:50:49.151 IST [1778802] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-10 11:50:49.151 IST [1778796] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:49.157 IST [1778803] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping publication "pub_new2" in database "db2"
pg_createsubscriber: creating subscription "pg_createsubscriber_16386_46bc8ee7" in database "db2"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "db2"
pg_createsubscriber: enabling subscription "pg_createsubscriber_16386_46bc8ee7" in database "db2"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:49.271 IST [1778796] LOG:  received fast shutdown request
2025-10-10 11:50:49.275 IST [1778796] LOG:  aborting any active transactions
2025-10-10 11:50:49.275 IST [1778803] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:49.280 IST [1778800] LOG:  shutting down
2025-10-10 11:50:49.293 IST [1778796] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474224418059343 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

==================== TEST CASE 3 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" -d db1 --publication pub_exists1 --clean=publications --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:49.416 IST [1778824] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:49.420 IST [1778824] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:49.431 IST [1778830] LOG:  database system was shut down in recovery at 2025-10-10 11:50:49 IST
2025-10-10 11:50:49.431 IST [1778830] LOG:  entering standby mode
2025-10-10 11:50:49.438 IST [1778830] LOG:  redo starts at 0/03000028
2025-10-10 11:50:49.438 IST [1778830] LOG:  consistent recovery state reached at 0/04000228
2025-10-10 11:50:49.438 IST [1778824] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:49.438 IST [1778830] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-10 11:50:49.444 IST [1778831] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:49.560 IST [1778824] LOG:  received fast shutdown request
2025-10-10 11:50:49.563 IST [1778824] LOG:  aborting any active transactions
2025-10-10 11:50:49.563 IST [1778831] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:49.569 IST [1778828] LOG:  shutting down
2025-10-10 11:50:49.583 IST [1778824] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pub_exists1" in database "db1"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16385_3cb3bdf7" in database "db1" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:49.710 IST [1778843] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:49.712 IST [1778843] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:49.724 IST [1778849] LOG:  database system was shut down in recovery at 2025-10-10 11:50:49 IST
2025-10-10 11:50:49.724 IST [1778849] LOG:  entering standby mode
2025-10-10 11:50:49.729 IST [1778849] LOG:  redo starts at 0/03000028
2025-10-10 11:50:49.729 IST [1778849] LOG:  consistent recovery state reached at 0/04000228
2025-10-10 11:50:49.729 IST [1778843] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:49.729 IST [1778849] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-10 11:50:49.734 IST [1778850] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping all existing publications in database "db1"
pg_createsubscriber: dropping publication "pub_existsa" in database "db1"
pg_createsubscriber: dropping publication "pub_existsb" in database "db1"
pg_createsubscriber: dropping publication "pub_existsc" in database "db1"
pg_createsubscriber: dropping publication "pub_existsd" in database "db1"
pg_createsubscriber: dropping publication "pub_exists1" in database "db1"
pg_createsubscriber: creating subscription "pg_createsubscriber_16385_3cb3bdf7" in database "db1"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "db1"
pg_createsubscriber: enabling subscription "pg_createsubscriber_16385_3cb3bdf7" in database "db1"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:49.852 IST [1778843] LOG:  received fast shutdown request
2025-10-10 11:50:49.855 IST [1778843] LOG:  aborting any active transactions
2025-10-10 11:50:49.855 IST [1778850] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:49.862 IST [1778847] LOG:  shutting down
2025-10-10 11:50:49.879 IST [1778843] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474226794206334 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

==================== TEST CASE 4 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" -d db1 --publication pub_exists1 --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:49.997 IST [1778871] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:49.999 IST [1778871] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:50.010 IST [1778877] LOG:  database system was shut down in recovery at 2025-10-10 11:50:49 IST
2025-10-10 11:50:50.012 IST [1778877] LOG:  entering standby mode
2025-10-10 11:50:50.016 IST [1778877] LOG:  redo starts at 0/03000028
2025-10-10 11:50:50.016 IST [1778877] LOG:  consistent recovery state reached at 0/04000228
2025-10-10 11:50:50.016 IST [1778871] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:50.016 IST [1778877] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-10 11:50:50.022 IST [1778878] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:50.140 IST [1778871] LOG:  received fast shutdown request
2025-10-10 11:50:50.144 IST [1778871] LOG:  aborting any active transactions
2025-10-10 11:50:50.145 IST [1778878] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:50.151 IST [1778875] LOG:  shutting down
2025-10-10 11:50:50.163 IST [1778871] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pub_exists1" in database "db1"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16385_7fe11ccf" in database "db1" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:50.290 IST [1778890] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:50.292 IST [1778890] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:50.306 IST [1778896] LOG:  database system was shut down in recovery at 2025-10-10 11:50:50 IST
2025-10-10 11:50:50.307 IST [1778896] LOG:  entering standby mode
2025-10-10 11:50:50.310 IST [1778896] LOG:  redo starts at 0/03000028
2025-10-10 11:50:50.310 IST [1778896] LOG:  consistent recovery state reached at 0/04000428
2025-10-10 11:50:50.310 IST [1778896] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-10 11:50:50.311 IST [1778890] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:50.319 IST [1778897] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping publication "pub_exists1" in database "db1"
pg_createsubscriber: creating subscription "pg_createsubscriber_16385_7fe11ccf" in database "db1"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "db1"
pg_createsubscriber: enabling subscription "pg_createsubscriber_16385_7fe11ccf" in database "db1"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:50.430 IST [1778890] LOG:  received fast shutdown request
2025-10-10 11:50:50.436 IST [1778890] LOG:  aborting any active transactions
2025-10-10 11:50:50.436 IST [1778897] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:50.440 IST [1778894] LOG:  shutting down
2025-10-10 11:50:50.455 IST [1778890] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474229361685677 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

==================== TEST CASE 5 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" --clean=publications --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: no database was specified
pg_createsubscriber: database name "postgres" was extracted from the publisher connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:50.580 IST [1778918] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:50.582 IST [1778918] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:50.595 IST [1778924] LOG:  database system was shut down in recovery at 2025-10-10 11:50:50 IST
2025-10-10 11:50:50.596 IST [1778924] LOG:  entering standby mode
2025-10-10 11:50:50.599 IST [1778924] LOG:  redo starts at 0/03000028
2025-10-10 11:50:50.599 IST [1778924] LOG:  consistent recovery state reached at 0/04000428
2025-10-10 11:50:50.599 IST [1778924] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-10 11:50:50.599 IST [1778918] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:50.608 IST [1778925] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:50.720 IST [1778918] LOG:  received fast shutdown request
2025-10-10 11:50:50.726 IST [1778918] LOG:  aborting any active transactions
2025-10-10 11:50:50.726 IST [1778925] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:50.732 IST [1778922] LOG:  shutting down
2025-10-10 11:50:50.745 IST [1778918] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pg_createsubscriber_5_4d34547a" in database "postgres"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_5_4d34547a" in database "postgres" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:50.869 IST [1778937] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:50.872 IST [1778937] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:50.885 IST [1778943] LOG:  database system was shut down in recovery at 2025-10-10 11:50:50 IST
2025-10-10 11:50:50.885 IST [1778943] LOG:  entering standby mode
2025-10-10 11:50:50.889 IST [1778943] LOG:  redo starts at 0/03000028
2025-10-10 11:50:50.890 IST [1778943] LOG:  consistent recovery state reached at 0/04000428
2025-10-10 11:50:50.890 IST [1778943] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-10 11:50:50.890 IST [1778937] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:50.900 IST [1778944] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping all existing publications in database "postgres"
pg_createsubscriber: dropping publication "pub_existsa" in database "postgres"
pg_createsubscriber: dropping publication "pub_existsb" in database "postgres"
pg_createsubscriber: dropping publication "pub_existsc" in database "postgres"
pg_createsubscriber: dropping publication "pub_existsd" in database "postgres"
pg_createsubscriber: dropping publication "pg_createsubscriber_5_4d34547a" in database "postgres"
pg_createsubscriber: creating subscription "pg_createsubscriber_5_4d34547a" in database "postgres"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "postgres"
pg_createsubscriber: enabling subscription "pg_createsubscriber_5_4d34547a" in database "postgres"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:51.038 IST [1778937] LOG:  received fast shutdown request
2025-10-10 11:50:51.041 IST [1778937] LOG:  aborting any active transactions
2025-10-10 11:50:51.041 IST [1778944] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:51.044 IST [1778943] LOG:  invalid record length at 0/04000628: expected at least 24, got 0
2025-10-10 11:50:51.048 IST [1778941] LOG:  shutting down
2025-10-10 11:50:51.062 IST [1778937] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474232046916828 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

==================== TEST CASE 6 ====================
Command: ./pg_createsubscriber -D standby/ -P "host=localhost port=5432 dbname=postgres" --dry-run --verbose
pg_createsubscriber: validating publisher connection string
pg_createsubscriber: validating subscriber connection string
pg_createsubscriber: no database was specified
pg_createsubscriber: database name "postgres" was extracted from the publisher connection string
pg_createsubscriber: checking if directory "standby" is a cluster data directory
pg_createsubscriber: getting system identifier from publisher
pg_createsubscriber: system identifier is 7559474169502327738 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7559474169502327738 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-10 11:50:51.185 IST [1778965] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:51.187 IST [1778965] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:51.198 IST [1778971] LOG:  database system was shut down in recovery at 2025-10-10 11:50:51 IST
2025-10-10 11:50:51.200 IST [1778971] LOG:  entering standby mode
2025-10-10 11:50:51.204 IST [1778971] LOG:  redo starts at 0/03000028
2025-10-10 11:50:51.204 IST [1778971] LOG:  consistent recovery state reached at 0/04000628
2025-10-10 11:50:51.204 IST [1778971] LOG:  invalid record length at 0/04000628: expected at least 24, got 0
2025-10-10 11:50:51.204 IST [1778965] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:51.213 IST [1778972] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
pg_createsubscriber: checking settings on publisher
pg_createsubscriber: warning: two_phase option will not be enabled for replication slots
pg_createsubscriber: detail: Subscriptions will be created with the two_phase option disabled.  Prepared transactions will be replicated at COMMIT PREPARED.
pg_createsubscriber: hint: You can use the command-line option --enable-two-phase to enable two_phase.
pg_createsubscriber: warning: required WAL could be removed from the publisher
pg_createsubscriber: hint: Set the configuration parameter "max_slot_wal_keep_size" to -1 to ensure that required WAL files are not prematurely removed.
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:51.323 IST [1778965] LOG:  received fast shutdown request
2025-10-10 11:50:51.326 IST [1778965] LOG:  aborting any active transactions
2025-10-10 11:50:51.326 IST [1778972] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:51.332 IST [1778969] LOG:  shutting down
2025-10-10 11:50:51.346 IST [1778965] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pg_createsubscriber_5_39424800" in database "postgres"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_5_39424800" in database "postgres" on publisher
pg_createsubscriber: starting the subscriber
2025-10-10 11:50:51.472 IST [1778984] LOG:  starting PostgreSQL 19devel on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2025-10-10 11:50:51.474 IST [1778984] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-10 11:50:51.486 IST [1778990] LOG:  database system was shut down in recovery at 2025-10-10 11:50:51 IST
2025-10-10 11:50:51.487 IST [1778990] LOG:  entering standby mode
2025-10-10 11:50:51.490 IST [1778990] LOG:  redo starts at 0/03000028
2025-10-10 11:50:51.491 IST [1778990] LOG:  consistent recovery state reached at 0/04000628
2025-10-10 11:50:51.491 IST [1778984] LOG:  database system is ready to accept read-only connections
2025-10-10 11:50:51.491 IST [1778990] LOG:  invalid record length at 0/04000628: expected at least 24, got 0
2025-10-10 11:50:51.496 IST [1778991] LOG:  started streaming WAL from primary at 0/04000000 on timeline 1
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
pg_createsubscriber: target server reached the consistent state
pg_createsubscriber: hint: If pg_createsubscriber fails after this point, you must recreate the physical replica before continuing.
pg_createsubscriber: dropping publication "pg_createsubscriber_5_39424800" in database "postgres"
pg_createsubscriber: creating subscription "pg_createsubscriber_5_39424800" in database "postgres"
pg_createsubscriber: setting the replication progress (node name "pg_0", LSN 0/00000000) in database "postgres"
pg_createsubscriber: enabling subscription "pg_createsubscriber_5_39424800" in database "postgres"
pg_createsubscriber: stopping the subscriber
2025-10-10 11:50:51.608 IST [1778984] LOG:  received fast shutdown request
2025-10-10 11:50:51.611 IST [1778984] LOG:  aborting any active transactions
2025-10-10 11:50:51.611 IST [1778991] FATAL:  terminating walreceiver process due to administrator command
2025-10-10 11:50:51.616 IST [1778988] LOG:  shutting down
2025-10-10 11:50:51.634 IST [1778984] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7559474234385757451 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

========== All test cases completed ==========