On October 5, 2004 10:35 am, Christopher Browne wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Brad Hilton wrote:
> | hannu at skype.net wrote:
> |>> Hello,
> |>>
> |>> I've spent the last few days learning slony and setting it up on some
> |>> test databases with good results.  However, when I set up replication
> |>> on my live database, the slon processes startup and appear to be
> |>> preparing to copy things over when I get:
> |>>
> |>> "The postmaster has commanded this server process to roll back the
> |>> current transaction and exit, because another server process exited
> |>> abnormally and possibly corrupted shared memory."
> |>>
> |>> This happens continually until I uninstall the slony schema from my
> |>> database.
> |>
> |> Does slon  need to be running or is it happening even without it
> |> (maybe as
> |> a result of slony triggers doing something bad) ?
> |
> | No, slon does not need to be running for the crashes to occur.
>
> That's useful to know; that suggests that the reason for the problem may
> not directly relate to Slony-I.
They could be problems within the xxid.c and slony1_funcs.c C functions which 
provide the logging triggers.


>
> | I'll work on getting a stack trace.
>
> That should be helpful.
But yes this stack trace is all important (hopefully you have postgres built 
with debugging symbols)
 

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBYttECVn6LJfHIAIRAlX0AJ4mYtr/SvEpMbXZNaPFOr7kg2KIywCeMAbN
> iQbtPe3EtZBEUZn1ako4aMc=
> =DQ+j
> -----END PGP SIGNATURE-----
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx:  250.763.1759
http://www.wavefire.com