From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Ensure that snprintf.c's fmtint() doesn't overflow when printing
Date: Wed, 03 Oct 2018 16:24:23 -0400
Message-ID: <527.1538598263@sss.pgh.pa.us> (raw)
In-Reply-To: <E1g7nZU-0000kU-MB@gemulon.postgresql.org>
References: <E1g7nZU-0000kU-MB@gemulon.postgresql.org>
Andres Freund <andres@anarazel.de> writes:
> Ensure that snprintf.c's fmtint() doesn't overflow when printing INT64_MIN.
Hm, I think you should s/uint64/unsigned long long/ to be consistent
with 595a0eab7.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Ensure that snprintf.c's fmtint() doesn't overflow when printing
In-Reply-To: <527.1538598263@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox