issue2550549 Postgres error on message templating Exception gets thrown and not captured if nodeid is too large on postgres. Added a check in rdbms_common layer that max nodeid is < 2^31 -1. This is also the limit for INTEGER on MySql. SqlLite can support up to 2^63-1, but I chose the smallest common denominator. Large nodeid should now returns no such id rather than a stack trace. Patch idea from: martin.v.loewis. (John Rouillard) This fixes the reason for patches: https://hg.python.org/tracker/roundup/rev/1548763e8273 and https://hg.python.org/tracker/roundup/rev/eb3be57f1ef2

<!--
 This is the default body that is displayed when people visit the
 tracker. The tag below lists the currently open issues. You may
 replace it with a greeting message, or a different list of issues or
 whatever. It's a good idea to have the issues on the front page though
-->
<span tal:replace="structure python:db.issue.renderWith('index',
    sort=[('-', 'activity')], filter=['status'],
    columns=['activity','title','creator'],
    filterspec={'status':['1','2','4']})" />