The test case in msg3710 returns a plain


   There is no issue with id 32132132131 

error, so the question is is this patch needed in the current
roundup? Maybe the underlying issue that caused postgres to fail
is fixed?

(or Maybe roundup.org isn't using postgres so there is no way to
reproduce the original error using it).

Also this patch seems to be getting applied at the wrong level.
If postgres is choking on id's larger than 2^30, shouldn't
this patch be in the postgres database back end so that

   if not cl.hasnode(id):

returns false?