This looks very similar. I'll leave a comment to this effect on the bug. Thanks!

For what it's worth, I tried restarting the slon daemon on both the master & slave. I got a very similar error, but this time it was complaining that "Lost Angeles" wasn't an integer.

- Matt


-----Original Message-----
From: Steve Singer [mailto:ssinger at ca.afilias.info] 
Sent: Friday, January 24, 2014 9:59 AM
To: Jan Wieck
Cc: Hanselman, Matthew; slony1-general at lists.slony.info
Subject: Re: [Slony1-general] Sync stopped with slony-2.2.1 on data type mismatch

On 01/23/2014 03:42 PM, Jan Wieck wrote:
> On 01/23/14 15:31, Hanselman, Matthew wrote:
>> Running Slony 2.2.1 with Postgres 9.2.6. The slave is getting errors 
>> trying to apply a change with this error:
>>
>>
>>
>> 2014-01-23 14:55:58 EST ERROR  remoteWorkerThread_1_1: error at end 
>> of COPY IN: ERROR:  invalid input syntax for integer: "33.7726910000000018"
>>


Could this be the same thing as that is causing
http://bugs.slony.info/bugzilla/show_bug.cgi?id=327

(We suspect memory corruption in the apply trigger)




>>
>>
>> The column in question is a "double precision" on both master & slave.
>> No schema change has happened since Slony was deployed.
>
> What did happen between slony was deployed and this breakage?
>
>
> Jan
>
>
>
>>
>>
>>
>> Is this a bug in Slony, or is there something else I can do to troubleshoot?
>>
>>
>>
>> - Matt
>>
>>
>>
>>
>>
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at lists.slony.info
>> http://lists.slony.info/mailman/listinfo/slony1-general
>>
>
>