pgsql: Make sure that GIN fast-insert and regular code paths enforce the

Log Message:
-----------
Make sure that GIN fast-insert and regular code paths enforce the same
tuple size limit. Improve the error message for index-tuple-too-large
so that it includes the actual size, the limit, and the index name.
Sync with the btree occurrences of the same error.

Back-patch to 8.4 because it appears that the out-of-sync problem
is occurring in the field.

Teodor and Tom

Tags:
----
REL8_4_STABLE

Modified Files:
--------------
pgsql/src/backend/access/gin:
ginentrypage.c (r1.21 -> r1.21.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginentrypage.c?r1=1.21&r2=1.21.2.1)
ginfast.c (r1.3.2.1 -> r1.3.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginfast.c?r1=1.3.2.1&r2=1.3.2.2)
gininsert.c (r1.22 -> r1.22.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/gininsert.c?r1=1.22&r2=1.22.2.1)
ginvacuum.c (r1.30 -> r1.30.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginvacuum.c?r1=1.30&r2=1.30.2.1)
pgsql/src/backend/access/nbtree:
nbtinsert.c (r1.170 -> r1.170.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtinsert.c?r1=1.170&r2=1.170.2.1)
nbtsort.c (r1.119 -> r1.119.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtsort.c?r1=1.119&r2=1.119.2.1)
pgsql/src/include/access:
gin.h (r1.34 -> r1.34.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gin.h?r1=1.34&r2=1.34.2.1)