http://www.slony.info/bugzilla/show_bug.cgi?id=155

           Summary: slon can segfault when the postgres backend abnormally
                    terminates
           Product: Slony-I
           Version: 2.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: low
         Component: slon
        AssignedTo: slony1-bugs at lists.slony.info
        ReportedBy: ssinger at ca.afilias.info
                CC: slony1-bugs at lists.slony.info
   Estimated Hours: 0.0


If the postgresql backend slon is connected to terminates then slon can die
with a segfault.

The following was observed during testing with tests that intentionally kill
the backend.

2010-09-08 17:19:46,866 [main] INFO 
info.slony.clustertest.testcoordinator.Coordinator  - terminating backend
2010-09-08 17:19:46,864 [db3 stdout] DEBUG
info.slony.clustertest.testcoordinator.slony.SlonLauncher db3 - 2010-09-08
17:19:46 CUTER
ROR  remoteListenThread_1: "select con_origin, con_received,     max(con_seqno)
as con_seqno,     max(con_timestamp) as con_timestam
p from "_disorder_replica".sl_confirm where con_received <> 3 group by
con_origin, con_received" 2010-09-08 17:19:46 CUTCONFIG slon:
 child terminated status: 11; pid: 249898, current worker pid: 249898


Slon should probably exit on an error code with this happens not segfault.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.