Thanks for the quick response. I'll give the rebuild on the remote server a try.
I am aware of the age of 7.4.6, and upgrading is definitely on my list but I haven't had the time to research and test what to move up to. Any recommendations? I believe the step up in 7.4.x would be to 7.4.11, but I'm not opposed to moving up to 8.x... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew Sullivan Sent: Thursday, June 29, 2006 10:46 AM To: [email protected] Subject: Re: [Slony1-general] Having problem with initial copy On Thu, Jun 29, 2006 at 10:41:47AM -0400, Sean Kirkpatrick wrote: > > I've been successfully using slony (1.0.5) to replicate several > 7.4.6 databases to various numbers of nodes for about 6 months now, Off-topic, but you are aware that 7.4.6 is a _long_ way back in the minor release chain, right? You want to upgrade that really soon. > ERROR remoteWorkerThread_1: copy from stdin on local node - > PGRES_FATAL_ERROR ERROR: invalid input syntax fo > r integer: "t" > CONTEXT: COPY tlcalerttbl, line 1, column marketstate: "t" > > It appears that the column values are misaligned somewhere in the > copy. This isn't the table that the primary key was changed on > either. I think you need to re-build the schema on the remote system. I forget which version introduced column names in the COPY command, but that would also help you (and you wouldn't need the schema rebuild). A -- Andrew Sullivan | [EMAIL PROTECTED] Unfortunately reformatting the Internet is a little more painful than reformatting your hard drive when it gets out of whack. --Scott Morris _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
