Results.log

application/octet-stream
Filename: Results.log
Type: application/octet-stream
Part: 1
Message: Re: Add support for specifying tables in pg_createsubscriber.
==================== 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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:41.868 IST [1800129] 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-13 08:57:41.873 IST [1800129] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:41.883 IST [1800135] LOG:  database system was shut down in recovery at 2025-10-13 08:57:41 IST
2025-10-13 08:57:41.884 IST [1800135] LOG:  entering standby mode
2025-10-13 08:57:41.887 IST [1800135] LOG:  redo starts at 0/03000028
2025-10-13 08:57:41.887 IST [1800135] LOG:  consistent recovery state reached at 0/04000000
2025-10-13 08:57:41.887 IST [1800129] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:41.895 IST [1800136] 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-13 08:57:42.009 IST [1800129] LOG:  received fast shutdown request
2025-10-13 08:57:42.014 IST [1800129] LOG:  aborting any active transactions
2025-10-13 08:57:42.014 IST [1800136] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:42.019 IST [1800133] LOG:  shutting down
2025-10-13 08:57:42.033 IST [1800129] 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_3feed974" in database "db2" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:42.159 IST [1800148] 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-13 08:57:42.164 IST [1800148] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:42.176 IST [1800154] LOG:  database system was shut down in recovery at 2025-10-13 08:57:42 IST
2025-10-13 08:57:42.178 IST [1800154] LOG:  entering standby mode
2025-10-13 08:57:42.182 IST [1800154] LOG:  redo starts at 0/03000028
2025-10-13 08:57:42.182 IST [1800154] LOG:  consistent recovery state reached at 0/04000000
2025-10-13 08:57:42.182 IST [1800148] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:42.188 IST [1800155] 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_3feed974" 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_3feed974" in database "db2"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:42.341 IST [1800148] LOG:  received fast shutdown request
2025-10-13 08:57:42.353 IST [1800148] LOG:  aborting any active transactions
2025-10-13 08:57:42.353 IST [1800155] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:42.360 IST [1800152] LOG:  shutting down
2025-10-13 08:57:42.419 IST [1800148] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542868399814583 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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:42.487 IST [1800176] 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-13 08:57:42.489 IST [1800176] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:42.501 IST [1800182] LOG:  database system was shut down in recovery at 2025-10-13 08:57:42 IST
2025-10-13 08:57:42.502 IST [1800182] LOG:  entering standby mode
2025-10-13 08:57:42.505 IST [1800182] LOG:  redo starts at 0/03000028
2025-10-13 08:57:42.505 IST [1800182] LOG:  consistent recovery state reached at 0/04000000
2025-10-13 08:57:42.505 IST [1800176] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:42.511 IST [1800183] 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-13 08:57:42.626 IST [1800176] LOG:  received fast shutdown request
2025-10-13 08:57:42.629 IST [1800176] LOG:  aborting any active transactions
2025-10-13 08:57:42.629 IST [1800183] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:42.631 IST [1800182] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-13 08:57:42.636 IST [1800180] LOG:  shutting down
2025-10-13 08:57:42.650 IST [1800176] 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_47853f18" in database "db2" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:42.772 IST [1800195] 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-13 08:57:42.775 IST [1800195] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:42.786 IST [1800201] LOG:  database system was shut down in recovery at 2025-10-13 08:57:42 IST
2025-10-13 08:57:42.788 IST [1800201] LOG:  entering standby mode
2025-10-13 08:57:42.792 IST [1800201] LOG:  redo starts at 0/03000028
2025-10-13 08:57:42.792 IST [1800201] LOG:  consistent recovery state reached at 0/04000228
2025-10-13 08:57:42.792 IST [1800195] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:42.792 IST [1800201] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-13 08:57:42.798 IST [1800202] 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_47853f18" 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_47853f18" in database "db2"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:42.911 IST [1800195] LOG:  received fast shutdown request
2025-10-13 08:57:42.914 IST [1800195] LOG:  aborting any active transactions
2025-10-13 08:57:42.914 IST [1800202] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:42.919 IST [1800199] LOG:  shutting down
2025-10-13 08:57:42.933 IST [1800195] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542870931924966 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_existsa --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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:43.055 IST [1800223] 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-13 08:57:43.060 IST [1800223] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:43.072 IST [1800229] LOG:  database system was shut down in recovery at 2025-10-13 08:57:42 IST
2025-10-13 08:57:43.073 IST [1800229] LOG:  entering standby mode
2025-10-13 08:57:43.079 IST [1800229] LOG:  redo starts at 0/03000028
2025-10-13 08:57:43.079 IST [1800229] LOG:  consistent recovery state reached at 0/04000228
2025-10-13 08:57:43.079 IST [1800229] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-13 08:57:43.079 IST [1800223] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:43.084 IST [1800230] 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-13 08:57:43.206 IST [1800223] LOG:  received fast shutdown request
2025-10-13 08:57:43.214 IST [1800223] LOG:  aborting any active transactions
2025-10-13 08:57:43.214 IST [1800230] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:43.222 IST [1800227] LOG:  shutting down
2025-10-13 08:57:43.235 IST [1800223] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: use existing publication "pub_existsa" in database "db1"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16385_9ed7b154" in database "db1" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:43.352 IST [1800242] 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-13 08:57:43.354 IST [1800242] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:43.366 IST [1800248] LOG:  database system was shut down in recovery at 2025-10-13 08:57:43 IST
2025-10-13 08:57:43.366 IST [1800248] LOG:  entering standby mode
2025-10-13 08:57:43.370 IST [1800248] LOG:  redo starts at 0/03000028
2025-10-13 08:57:43.370 IST [1800248] LOG:  consistent recovery state reached at 0/04000228
2025-10-13 08:57:43.370 IST [1800248] LOG:  invalid record length at 0/04000228: expected at least 24, got 0
2025-10-13 08:57:43.370 IST [1800242] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:43.376 IST [1800249] 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: creating subscription "pg_createsubscriber_16385_9ed7b154" 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_9ed7b154" in database "db1"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:43.494 IST [1800242] LOG:  received fast shutdown request
2025-10-13 08:57:43.500 IST [1800242] LOG:  aborting any active transactions
2025-10-13 08:57:43.500 IST [1800249] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:43.502 IST [1800248] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-13 08:57:43.505 IST [1800246] LOG:  shutting down
2025-10-13 08:57:43.519 IST [1800242] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542873321621525 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_existsa --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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:43.641 IST [1800270] 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-13 08:57:43.643 IST [1800270] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:43.655 IST [1800276] LOG:  database system was shut down in recovery at 2025-10-13 08:57:43 IST
2025-10-13 08:57:43.655 IST [1800276] LOG:  entering standby mode
2025-10-13 08:57:43.659 IST [1800276] LOG:  redo starts at 0/03000028
2025-10-13 08:57:43.659 IST [1800276] LOG:  consistent recovery state reached at 0/04000428
2025-10-13 08:57:43.659 IST [1800270] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:43.659 IST [1800276] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-13 08:57:43.664 IST [1800277] 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-13 08:57:43.779 IST [1800270] LOG:  received fast shutdown request
2025-10-13 08:57:43.782 IST [1800270] LOG:  aborting any active transactions
2025-10-13 08:57:43.782 IST [1800277] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:43.788 IST [1800274] LOG:  shutting down
2025-10-13 08:57:43.800 IST [1800270] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: use existing publication "pub_existsa" in database "db1"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_16385_3e8d5f36" in database "db1" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:43.926 IST [1800289] 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-13 08:57:43.928 IST [1800289] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:43.939 IST [1800295] LOG:  database system was shut down in recovery at 2025-10-13 08:57:43 IST
2025-10-13 08:57:43.941 IST [1800295] LOG:  entering standby mode
2025-10-13 08:57:43.944 IST [1800295] LOG:  redo starts at 0/03000028
2025-10-13 08:57:43.945 IST [1800295] LOG:  consistent recovery state reached at 0/04000428
2025-10-13 08:57:43.945 IST [1800289] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:43.945 IST [1800295] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-13 08:57:43.950 IST [1800296] 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: preserve existing publication "pub_existsa" in database "db1"
pg_createsubscriber: creating subscription "pg_createsubscriber_16385_3e8d5f36" 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_3e8d5f36" in database "db1"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:44.063 IST [1800289] LOG:  received fast shutdown request
2025-10-13 08:57:44.066 IST [1800289] LOG:  aborting any active transactions
2025-10-13 08:57:44.066 IST [1800296] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:44.074 IST [1800293] LOG:  shutting down
2025-10-13 08:57:44.087 IST [1800289] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542875849435204 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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:44.207 IST [1800317] 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-13 08:57:44.214 IST [1800317] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:44.234 IST [1800323] LOG:  database system was shut down in recovery at 2025-10-13 08:57:44 IST
2025-10-13 08:57:44.235 IST [1800323] LOG:  entering standby mode
2025-10-13 08:57:44.238 IST [1800323] LOG:  redo starts at 0/03000028
2025-10-13 08:57:44.239 IST [1800323] LOG:  consistent recovery state reached at 0/04000428
2025-10-13 08:57:44.239 IST [1800323] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-13 08:57:44.239 IST [1800317] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:44.246 IST [1800324] 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-13 08:57:44.360 IST [1800317] LOG:  received fast shutdown request
2025-10-13 08:57:44.365 IST [1800317] LOG:  aborting any active transactions
2025-10-13 08:57:44.365 IST [1800324] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:44.371 IST [1800321] LOG:  shutting down
2025-10-13 08:57:44.385 IST [1800317] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pg_createsubscriber_5_48ab5991" in database "postgres"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_5_48ab5991" in database "postgres" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:44.512 IST [1800336] 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-13 08:57:44.518 IST [1800336] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:44.542 IST [1800342] LOG:  database system was shut down in recovery at 2025-10-13 08:57:44 IST
2025-10-13 08:57:44.542 IST [1800342] LOG:  entering standby mode
2025-10-13 08:57:44.551 IST [1800342] LOG:  redo starts at 0/03000028
2025-10-13 08:57:44.551 IST [1800342] LOG:  consistent recovery state reached at 0/04000428
2025-10-13 08:57:44.551 IST [1800342] LOG:  invalid record length at 0/04000428: expected at least 24, got 0
2025-10-13 08:57:44.551 IST [1800336] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:44.558 IST [1800343] 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_48ab5991" in database "postgres"
pg_createsubscriber: creating subscription "pg_createsubscriber_5_48ab5991" 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_48ab5991" in database "postgres"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:44.661 IST [1800336] LOG:  received fast shutdown request
2025-10-13 08:57:44.664 IST [1800336] LOG:  aborting any active transactions
2025-10-13 08:57:44.664 IST [1800343] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:44.671 IST [1800340] LOG:  shutting down
2025-10-13 08:57:44.685 IST [1800336] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542878300088435 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 7560542817875031889 on publisher
pg_createsubscriber: getting system identifier from subscriber
pg_createsubscriber: system identifier is 7560542817875031889 on subscriber
pg_createsubscriber: starting the standby server with command-line options
2025-10-13 08:57:44.805 IST [1800364] 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-13 08:57:44.808 IST [1800364] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:44.818 IST [1800370] LOG:  database system was shut down in recovery at 2025-10-13 08:57:44 IST
2025-10-13 08:57:44.821 IST [1800370] LOG:  entering standby mode
2025-10-13 08:57:44.825 IST [1800370] LOG:  redo starts at 0/03000028
2025-10-13 08:57:44.826 IST [1800370] LOG:  consistent recovery state reached at 0/04000628
2025-10-13 08:57:44.826 IST [1800364] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:44.826 IST [1800370] LOG:  invalid record length at 0/04000628: expected at least 24, got 0
2025-10-13 08:57:44.831 IST [1800371] 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-13 08:57:44.943 IST [1800364] LOG:  received fast shutdown request
2025-10-13 08:57:44.947 IST [1800364] LOG:  aborting any active transactions
2025-10-13 08:57:44.947 IST [1800371] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:44.952 IST [1800368] LOG:  shutting down
2025-10-13 08:57:44.967 IST [1800364] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: creating publication "pg_createsubscriber_5_cc463d05" in database "postgres"
pg_createsubscriber: creating the replication slot "pg_createsubscriber_5_cc463d05" in database "postgres" on publisher
pg_createsubscriber: starting the subscriber
2025-10-13 08:57:45.093 IST [1800383] 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-13 08:57:45.096 IST [1800383] LOG:  listening on Unix socket "/home/shubham/Project/Git/postgres/inst/bin/.s.PGSQL.50432"
2025-10-13 08:57:45.107 IST [1800389] LOG:  database system was shut down in recovery at 2025-10-13 08:57:44 IST
2025-10-13 08:57:45.110 IST [1800389] LOG:  entering standby mode
2025-10-13 08:57:45.113 IST [1800389] LOG:  redo starts at 0/03000028
2025-10-13 08:57:45.113 IST [1800389] LOG:  consistent recovery state reached at 0/04000628
2025-10-13 08:57:45.113 IST [1800383] LOG:  database system is ready to accept read-only connections
2025-10-13 08:57:45.113 IST [1800389] LOG:  invalid record length at 0/04000628: expected at least 24, got 0
2025-10-13 08:57:45.119 IST [1800390] 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_cc463d05" in database "postgres"
pg_createsubscriber: creating subscription "pg_createsubscriber_5_cc463d05" 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_cc463d05" in database "postgres"
pg_createsubscriber: stopping the subscriber
2025-10-13 08:57:45.234 IST [1800383] LOG:  received fast shutdown request
2025-10-13 08:57:45.237 IST [1800383] LOG:  aborting any active transactions
2025-10-13 08:57:45.238 IST [1800390] FATAL:  terminating walreceiver process due to administrator command
2025-10-13 08:57:45.242 IST [1800387] LOG:  shutting down
2025-10-13 08:57:45.256 IST [1800383] LOG:  database system is shut down
pg_createsubscriber: server was stopped
pg_createsubscriber: modifying system identifier of subscriber
pg_createsubscriber: system identifier is 7560542880849545378 on subscriber
pg_createsubscriber: running pg_resetwal on the subscriber
pg_createsubscriber: Done!

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