From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndQuadrant(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Timing events WIP v1 |
Date: | 2012-11-20 08:36:26 |
Message-ID: | 50AB410A.2030405@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/16/12 12:20 AM, Craig Ringer wrote:
> Not that implementing `hstore_to_json` is exactly hard, mind you, as a
> quick search shows: https://gist.github.com/2318757
Both pulling hstore more firmly into core and adopting something like a
hstore_to_json call as the preferred UI for timing event data are all
directions I'd be happy to go. That's why I stopped before trying to
even implement that part. I think the general direction to go is clear,
but the details on how to present the resulting data is more of a tarp
than even a bikeshed at this point. It's not a hard problem though.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-11-20 08:48:21 | Re: Timing events WIP v1 |
Previous Message | Kyotaro HORIGUCHI | 2012-11-20 07:44:39 | Re: the number of pending entries in GIN index with FASTUPDATE=on |