Re: Re: [COMMITTERS] pgsql: pg_test_timing utility, to measure clock monotonicity and timing
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Marko Kreen <markokr@gmail.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-03-28T12:57:42Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_test_timing utility, to measure clock monotonicity and timing cost.
- cee523867db2 9.2.0 cited
On Wed, Mar 28, 2012 at 8:51 AM, Marko Kreen <markokr@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 create a hazard for thirty-party code that wants to be cross-version, and for back-patching. We could work around that by doing something more complex, like creating additional symbols, but I'm thinking it ain't worth it just for this. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company