On Wed, Mar 28, 2012 at 10:43 AM, Fujii Masao masao.fu...@gmail.com wrote:
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
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
On Wed, Mar 28, 2012 at 08:19:37AM -0400, Robert Haas 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
On Wed, Mar 28, 2012 at 03:46:26PM +0300, Marko Kreen wrote:
On Wed, Mar 28, 2012 at 08:19:37AM -0400, Robert Haas 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
On Wed, Mar 28, 2012 at 8:51 AM, Marko Kreen mark...@gmail.com wrote:
How about: .. %10 INT64_FORMAT .. ?
Well, it won't work because unlike inttypes.h, Postgres *_FORMAT
includes '%' in it.
I guess that why inttypes.h does not do it...
Hmm, I guess we could change that, but it would
On Wed, Mar 28, 2012 at 08:57:42AM -0400, Robert Haas wrote:
On Wed, Mar 28, 2012 at 8:51 AM, Marko Kreen mark...@gmail.com wrote:
How about: .. %10 INT64_FORMAT .. ?
Well, it won't work because unlike inttypes.h, Postgres *_FORMAT
includes '%' in it.
I guess that why inttypes.h
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.
Fujii Masao masao.fu...@gmail.com writes:
This seems a simplest workaround. How about attached patch?
I think you need to tweak that to get the number to be right-justified
not left-justified.
regards, tom lane
--
Sent via pgsql-hackers mailing list
On Thu, Mar 29, 2012 at 12:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Fujii Masao masao.fu...@gmail.com writes:
This seems a simplest workaround. How about attached patch?
I think you need to tweak that to get the number to be right-justified
not left-justified.
Unless I'm missing something,
Fujii Masao masao.fu...@gmail.com writes:
On Thu, Mar 29, 2012 at 12:15 AM, Tom Lane t...@sss.pgh.pa.us wrote:
I think you need to tweak that to get the number to be right-justified
not left-justified.
Unless I'm missing something, I did that because the patch uses %10s
not %-10s. No?
Oh,
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.
Also I found one trivial problem in the doc of pg_test_timing. The
11 matches
Mail list logo
