Thu Jan 23 12:42:45 PST 2014
- Previous message: [Slony1-general] Sync stopped with slony-2.2.1 on data type mismatch
- Next message: [Slony1-general] Sync stopped with slony-2.2.1 on data type mismatch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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" > > > > 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 > -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] Sync stopped with slony-2.2.1 on data type mismatch
- Next message: [Slony1-general] Sync stopped with slony-2.2.1 on data type mismatch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list