aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-10-02 21:14:11 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-10-02 21:14:11 +0000
commitc3110e49b1601941e0173e8d75378f943b4ca6fd (patch)
tree3cb0a453fe9e193f38e8796e9281c8274bc96f28 /src/backend/parser/parse_expr.c
parentac317a8474e7c2e2c67ee37f8cb1a6511eb662d9 (diff)
downloadpostgresql-c3110e49b1601941e0173e8d75378f943b4ca6fd.tar.gz
postgresql-c3110e49b1601941e0173e8d75378f943b4ca6fd.zip
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
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions