Re: Timing events WIP v1
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Craig Ringer <craig@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2012-11-20T08:48:21Z
Lists: pgsql-hackers
2012/11/20 Greg Smith <greg@2ndquadrant.com>: > 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. > I don't like to see current hstore in core - It doesn't support nesting, it doesn't support different datatypes, it is not well supported by plpgsql regards Pavel > -- > Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD > PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers