]> granicus.if.org Git - postgresql/commit
Use snprintf not sprintf in pg_waldump's timestamptz_to_str.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 16 Jun 2018 18:45:47 +0000 (14:45 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 16 Jun 2018 18:45:47 +0000 (14:45 -0400)
commitf3be5d3e7891ef6886489cb0c9962d52c5983c70
treeb088e93de765fac9f91f3dbb8cc999916cbc57e1
parent2dbcf515ae1e8845d4903169ff81c91806c34d32
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
src/bin/pg_xlogdump/compat.c