On 10/5/2004 4:45 AM, hannu at skype.net wrote:
>> 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.

Not entirely sure how this could cause a crash, since slony doesn't 
cache those things that do change, but it is for sure possible. We'd 
need a stack trace or a test case to answer that question definitively.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #