> > 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
> 

Unfortunately, re-building the schema didn't help.  I recreated the database on the secondary server and reinitialized the schema from a pg_dump of the primary.  I then installed slony, started up both sides and issued the subscribe to start the initial copy.  Same error.

I tried using pg_dump to dump the data from the problem table using column inserts and the backup was able to process these as expected.

One thing to note here is that a column was added to a base table of the table with the problems.  That is the table with the issues inherits from a table where a column had just recently been added.  I'm wondering if COPY doesn't like that...

Any additional suggestions?

--Sean