Friendly greetings !

We've got a problem with slony segfaulting while replicating.
Because of a misplaced trigger (which wasn't supposed to be enabled)
on insert on a replicated table, that trigger was trying to create a
new entry every time slony was inserting a new row on this specific
table, and created a conflict :
postgres[3973]: [3-1] user=slony,db=ob2ERROR:duplicate key value
violates unique constraint "_article_counters_materialized_pkey"

In this case, according to the documentation, slony should PANIC, and it panic.
But instead of nicely exiting, it commit suicide with a segmentation fault.

kernel: slon[29305]: segfault at 0000000000000047 rip 00002b0e96f20580
rsp 00000000467f7858 error 4

Infortunaly, i don't have any good test case for you, as it happened
on production server.

Slony 1-2-15 (compiled from source)
Postgresql 8.3.6 (compiled from source)

Linux x64 Compiled from source, with custom patch. it's a Xen VM server.


-- 
F4FQM
Kerunix Flan
Laurent Laborde