aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeCustom.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-06-16 14:45:47 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-06-16 14:45:47 -0400
commitf3be5d3e7891ef6886489cb0c9962d52c5983c70 (patch)
treeb088e93de765fac9f91f3dbb8cc999916cbc57e1 /src/backend/executor/nodeCustom.c
parent2dbcf515ae1e8845d4903169ff81c91806c34d32 (diff)
downloadpostgresql-f3be5d3e7891ef6886489cb0c9962d52c5983c70.tar.gz
postgresql-f3be5d3e7891ef6886489cb0c9962d52c5983c70.zip
Use snprintf not sprintf in pg_waldump's timestamptz_to_str.
This could only cause an issue if strftime returned a ridiculously long timezone name, which seems unlikely; and it wouldn't qualify as a security problem even then, since pg_waldump (nee pg_xlogdump) is a debug tool not part of the server. But gcc 8 has started issuing warnings about it, so let's use snprintf and be safe. Backpatch to 9.3 where this code was added. Discussion: https://postgr.es/m/21789.1529170195@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeCustom.c')
0 files changed, 0 insertions, 0 deletions