Moving thread to -hackers, CC'ing Craig. Michael Paquier wrote:
> hamster complains here: > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamster&dt=2016-03-31%2016%3A00%3A06 > [...] > # Copying slots to replica > after_basebackup|test_decoding||547|0/5000060|0/5000098 > # Copying slot > 'after_basebackup','test_decoding',NULL,'547','0/5000060','0/5000098' > connection error: 'psql:<stdin>:1: server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > psql:<stdin>:1: connection to server was lost' Ahem. So, I see this: DEBUG: server process (PID 24166) exited with exit code 0 DEBUG: forked new backend, pid=24168 socket=7 LOG: statement: SELECT test_slot_timelines_advance_logical_slot('after_basebackup', NULL, '547', '0/5000060', '0/5000098'); DEBUG: server process (PID 24168) was terminated by signal 11: Segmentation fault DETAIL: Failed process was running: SELECT test_slot_timelines_advance_logical_slot('after_basebackup', NULL, '547', '0/5000060', '0/5000098'); LOG: server process (PID 24168) was terminated by signal 11: Segmentation fault in pgsql.build/src/test/recovery/tmp_check/log/006_logical_decoding_timelines_replica2.log Could you have a look at whether you have core dumps from these? If so, backtraces would be very useful. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
