On Wed, Mar 28, 2012 at 9:19 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Tue, Mar 27, 2012 at 10:10 PM, Fujii Masao <masao.fu...@gmail.com> wrote: >> On Wed, Mar 28, 2012 at 5:17 AM, Robert Haas <rh...@postgresql.org> wrote: >>> pg_test_timing utility, to measure clock monotonicity and timing cost. >> >> When I compiled this, I got a compiler warning. Attached patch >> silences the warning. > > Unfortunately, that *produces* a warning on my machine. Normally, I > think we handle this using INT64_FORMAT, but the fact that it's %10ld > here and not just %lld makes that awkward. I guess we maybe need to > insert some kludgy workaround here - write it into a separate buffer, > and then blank-pad it, or something like that.
This seems a simplest workaround. How about attached patch? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
pgtesttiming_int64format.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
