On 12/10/2012 7:09 PM, Tory M Blue wrote:
>
>
> On Mon, Dec 10, 2012 at 3:59 PM, Jan Wieck <JanWieck at yahoo.com
> <mailto:JanWieck at yahoo.com>> wrote:
>
>     On 12/10/2012 6:26 PM, Tory M Blue wrote:
>
>
>
>         On Mon, Dec 10, 2012 at 2:55 PM, Jan Wieck <JanWieck at yahoo.com
>         <mailto:JanWieck at yahoo.com>
>         <mailto:JanWieck at yahoo.com <mailto:JanWieck at yahoo.com>>> wrote:
>
>              On 12/10/2012 5:28 PM, Tory M Blue wrote:
>
>
>                  I'm back to it with debug of 4 on the source and the
>         destination
>                  nodes.
>
>                  Still failing
>
>                  Destination:
>
>                  Slon log:
>
>                  2012-12-10 12:04:49 PST CONFIG remoteWorkerThread_1:
>         6525.754
>                  seconds to
>                  copy table "cls"."listings"
>                  2012-12-10 12:04:49 PST CONFIG remoteWorkerThread_1:
>         copy table
>                  "cls"."customers"
>                  2012-12-10 12:04:49 PST CONFIG remoteWorkerThread_1:
>         Begin COPY
>                  of table
>                  "cls"."customers"
>                  2012-12-10 12:04:49 PST ERROR  remoteWorkerThread_1:
>         "select
>                  "_admissioncls".copyFields(8);____"
>
>
>     This is the bit that I don't understand.
>
>     Looking at the remote_worker.c code, this error message comes from
>     line 3032 in 2.1 STABLE. The same code is in line 2911 in HEAD.
>
>     That select of copyFields() has apparently failed, because the
>     result status code is not PGRES_TUPLES_OK, yet there seems to be
>     nothing returned from PQresultErrorMessage().
>
>     I wonder what PQresStatus(PQresultStatus(__res3)) as well as
>     PQerrorMessage(pro_dbconn) at this point have to tell.
>
>
>         Thanks for not giving up on me
>         Tory
>
>
>     What version of Slony are you running this on?
>
>
> -bash-4.1$ slon -v
> slon version 2.1.1
>
>
>     Can you run a custom patched slon on the new subscriber so that we
>     can see that information in the log?
>
>
> Absolutely!

Attached is a patch for 2.1.1 that adds that information to the error 
message. Since slon remains the same version, you only have to replace 
the slon binary on the new subscriber (node 10).


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Tory_M_Blue.1.diff
Type: text/x-patch
Size: 893 bytes
Desc: not available
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20121210/0556a316/attachment.bin