031_recovery_conflict_standby.log

text/plain

Filename: 031_recovery_conflict_standby.log
Type: text/plain
Part: 1
Message: Re: A failure in 031_recovery_conflict.pl on Debian/s390x
2023-08-10 01:00:49.463 UTC [892314] LOG:  starting PostgreSQL 17devel (Debian 17~~devel-1) on s390x-ibm-linux-gnu, compiled by gcc (Debian 13.2.0-1) 13.2.0, 64-bit
2023-08-10 01:00:49.463 UTC [892314] LOG:  listening on Unix socket "/tmp/5M7Y6uSm5n/.s.PGSQL.63014"
2023-08-10 01:00:49.465 UTC [892317] LOG:  database system was interrupted; last known up at 2023-08-10 01:00:48 UTC
2023-08-10 01:00:49.465 UTC [892317] LOG:  entering standby mode
2023-08-10 01:00:49.466 UTC [892317] LOG:  redo starts at 0/2000028
2023-08-10 01:00:49.466 UTC [892317] WARNING:  unexpected directory entry "16384" found in pg_tblspc/
2023-08-10 01:00:49.466 UTC [892317] DETAIL:  All directory entries in pg_tblspc/ should be symbolic links.
2023-08-10 01:00:49.466 UTC [892317] HINT:  Remove those directories, or set allow_in_place_tablespaces to ON transiently to let recovery complete.
2023-08-10 01:00:49.466 UTC [892317] LOG:  consistent recovery state reached at 0/2000100
2023-08-10 01:00:49.470 UTC [892314] LOG:  database system is ready to accept read-only connections
2023-08-10 01:00:49.494 UTC [892318] LOG:  started streaming WAL from primary at 0/3000000 on timeline 1
2023-08-10 01:00:49.773 UTC [892329] 031_recovery_conflict.pl LOG:  statement: BEGIN;
2023-08-10 01:00:49.774 UTC [892329] 031_recovery_conflict.pl LOG:  statement: DECLARE test_recovery_conflict_cursor CURSOR FOR SELECT b FROM test_recovery_conflict_table1;
2023-08-10 01:00:49.774 UTC [892329] 031_recovery_conflict.pl LOG:  statement: FETCH FORWARD FROM test_recovery_conflict_cursor;
2023-08-10 01:00:49.780 UTC [892329] 031_recovery_conflict.pl LOG:  statement: ;
2023-08-10 01:03:54.144 UTC [892318] FATAL:  could not receive data from WAL stream: server closed the connection unexpectedly
		This probably means the server terminated abnormally
		before or while processing the request.
2023-08-10 01:03:54.146 UTC [892317] LOG:  invalid record length at 0/347E6E0: expected at least 24, got 0
2023-08-10 01:03:54.153 UTC [892427] FATAL:  could not connect to the primary server: connection to server on socket "/tmp/5M7Y6uSm5n/.s.PGSQL.63013" failed: No such file or directory
		Is the server running locally and accepting connections on that socket?
2023-08-10 01:03:54.156 UTC [892317] LOG:  waiting for WAL to become available at 0/347E6F8
2023-08-10 01:03:54.248 UTC [892314] LOG:  received immediate shutdown request
2023-08-10 01:03:54.252 UTC [892314] LOG:  database system is shut down