> On 10/4/2004 8:30 PM, Brad Hilton 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."

Similar things have happened to me when someone changed schema (added
columns) to master table directly, bypassing slonik.

---------------
Hannu