aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorJoe Conway <mail@joeconway.com>2019-12-23 13:33:25 -0500
committerJoe Conway <mail@joeconway.com>2019-12-23 13:33:25 -0500
commitd5b9c2baff662aac22cd2a497d5bcd3b5a916fd0 (patch)
treee9c9b4208bc62f2f729f2c54724f19a7bf335d8a /src/backend/access/gist/gistbuild.c
parent39ebb943de9dd64e305d17329b8989e3061d03a5 (diff)
downloadpostgresql-d5b9c2baff662aac22cd2a497d5bcd3b5a916fd0.tar.gz
postgresql-d5b9c2baff662aac22cd2a497d5bcd3b5a916fd0.zip
Disallow null category in crosstab_hash
While building a hash map of categories in load_categories_hash, resulting category names have not thus far been checked to ensure they are not null. Prior to pg12 null category names worked to the extent that they did not crash on some platforms. This is because those system libraries have an snprintf which can deal with being passed a null pointer argument for a string. But even in those cases null categories did nothing useful. And on some platforms it crashed. As of pg12, our own version of snprintf gets called, and it does not deal with null pointer arguments at all, and crashes consistently. Fix that by disallowing null categories. They never worked usefully, and no one has ever asked for them to work previously. Back-patch to all supported branches. Reported-By: Ireneusz Pluta Discussion: https://postgr.es/m/16176-7489719b05e4303c@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions