Alexander Kolodziej wrote:
> Hello!

> There is a 1.2.16 version of Slony available for Postgres 8.3 in Ubuntu.
> Any chance that that could solve the problem? Other options i see are
> too dump/restore the master DB. Other than that... Any ideas? :)
> 
>   wbr / Alex
> 
> So it segfaults while logging?

This looks somewhat like bug # 55.

This was fixed in 1.2.21 try slony version 1.2.21 to see if it fixes 
your problem.


The other thing you might try doing is set the slon log level to 
something lower (less logging), to not trigger the bug.



> ===================================================================
> Core was generated by `/usr/bin/slon -f /etc/slony1/bigdb/slon.conf -p
> /var/run/slony1/bigdb'.
> Program terminated with signal 11, Segmentation fault.
> [New process 31964]
> [New process 31965]
> [New process 31966]
> [New process 31949]
> [New process 31967]
> [New process 31971]
> [New process 31954]
> [New process 31952]
> #0  0x00007fcfd5e37c40 in strlen () from /lib/libc.so.6
> (gdb) bt
> #0  0x00007fcfd5e37c40 in strlen () from /lib/libc.so.6
> #1  0x00007fcfd5e0075e in vfprintf () from /lib/libc.so.6
> #2  0x00007fcfd5eb3738 in __vsnprintf_chk () from /lib/libc.so.6
> #3  0x0000000000418764 in slon_log (level=<value optimized out>,
> fmt=0x420093 " ssy_action_list value: %s\n") at
> /usr/include/bits/stdio2.h:78
> #4  0x000000000040b4c5 in sync_event (node=0x1659f90, local_conn=<value
> optimized out>, wd=0x1659920, event=0x7fcfcc008f20) at remote_worker.c:4334
> #5  0x000000000040dcf8 in remoteWorkerThread_main (cdata=0x1659f90) at
> remote_worker.c:630
> #6  0x00007fcfd61303ba in start_thread () from /lib/libpthread.so.0
> #7  0x00007fcfd5e9cfcd in clone () from /lib/libc.so.6
> #8  0x0000000000000000 in ?? ()
> (gdb)
> ===================================================================
> 
> 
> 
> 

-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142