On 12/10/2012 7:09 PM, Tory M Blue wrote:


On Mon, Dec 10, 2012 at 3:59 PM, Jan Wieck <[email protected]
<mailto:[email protected]>> wrote:

    On 12/10/2012 6:26 PM, Tory M Blue wrote:



        On Mon, Dec 10, 2012 at 2:55 PM, Jan Wieck <[email protected]
        <mailto:[email protected]>
        <mailto:[email protected] <mailto:[email protected]>>> 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
diff --git a/src/slon/remote_worker.c b/src/slon/remote_worker.c
index 7fbf67c..3497008 100644
*** a/src/slon/remote_worker.c
--- b/src/slon/remote_worker.c
*************** copy_set(SlonNode *node, SlonConn *local
*** 3029,3037 ****
  
  		if (PQresultStatus(res3) != PGRES_TUPLES_OK)
  		{
! 			slon_log(SLON_ERROR, "remoteWorkerThread_%d: \"%s\" %s\n",
  					 node->no_id, dstring_data(&query2),
! 					 PQresultErrorMessage(res3));
  			PQclear(res3);
  			PQclear(res1);
  			slon_disconnectdb(pro_conn);
--- 3029,3039 ----
  
  		if (PQresultStatus(res3) != PGRES_TUPLES_OK)
  		{
! 			slon_log(SLON_ERROR, "remoteWorkerThread_%d: \"%s\" %s %s - %s\n",
  					 node->no_id, dstring_data(&query2),
! 					 PQresStatus(PQresultStatus(res3)),
! 					 PQresultErrorMessage(res3),
! 					 PQerrorMessage(pro_dbconn));
  			PQclear(res3);
  			PQclear(res1);
  			slon_disconnectdb(pro_conn);
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to