aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xloginsert.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-02-14 15:06:01 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-02-14 15:06:01 -0500
commit0c62356cc8777961221a643fa77f62e1c7361085 (patch)
tree264a983eb1d9b878083f353615ab2a9b9118953c /src/backend/access/transam/xloginsert.c
parente748e902def40ee52d1ef0b770fd24aa0835e304 (diff)
downloadpostgresql-0c62356cc8777961221a643fa77f62e1c7361085.tar.gz
postgresql-0c62356cc8777961221a643fa77f62e1c7361085.zip
Add an assertion that we don't pass NULL to snprintf("%s").
Per commit e748e902d, we appear to have little or no coverage in the buildfarm of machines that will dump core when asked to printf a null string pointer. Let's try to improve that situation by adding an assertion that will make src/port/snprintf.c behave that way. Since it's just an assertion, it won't break anything in production builds, but it will help developers find this type of oversight. Note that while our buildfarm coverage of machines that use that snprintf implementation is pretty thin on the Unix side (apparently amounting only to gaur/pademelon), all of the MSVC critters use it. Discussion: https://postgr.es/m/156b989dbc6fe7c4d3223cf51da61195@postgrespro.ru
Diffstat (limited to 'src/backend/access/transam/xloginsert.c')
0 files changed, 0 insertions, 0 deletions