summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-12-20 15:58:58 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-12-20 16:21:59 -0500
commit5bbee34d9f2e6097247ace3ebe1dde1f6aa80287 (patch)
tree8d59b45b36a5dd01e7135263e0bb161e753fe49e /src/backend/access/gist/gist.c
parent7b14bcc06cc56b110118fba408f4b9b72a663387 (diff)
downloadpostgresql-5bbee34d9f2e6097247ace3ebe1dde1f6aa80287.tar.gz
Avoid producing over-length specific_name outputs in information_schema.
information_schema output columns that are declared as being type sql_identifier are supposed to conform to the implementation's rules for valid identifiers, in particular the identifier length limit. Several places potentially violated this limit by concatenating a function's name and OID. (The OID is added to ensure name uniqueness within a schema, since the spec doesn't expect function name overloading.) Simply truncating the concatenation result to fit in "name" won't do, since losing part of the OID might wind up giving non-unique results. Instead, let's truncate the function name as necessary. The most practical way to do that is to do it in a C function; the information_schema.sql script doesn't have easy access to the value of NAMEDATALEN, nor does it have an easy way to truncate on the basis of resulting byte-length rather than number of characters. (There are still a couple of places that cast concatenation results to sql_identifier, but as far as I can see they are guaranteed not to produce over-length strings, at least with the normal value of NAMEDATALEN.) Discussion: https://postgr.es/m/23817.1545283477@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions