Re: Timing events WIP v1

<div class="moz-cite-prefix">On 11/16/2012 02:26 AM, Josh Berkus wrote:<br /></div><blockquote
cite="mid:50A533CC.6010805@agliodbs.com"type="cite"><pre wrap="">
 
</pre><blockquote type="cite"><pre wrap="">Extending this to save the key/value set and most of the other data I
mentioned before is pretty straightforward. 
</pre></blockquote><pre wrap="">
Why not use Hstore?  Seriously?
</pre></blockquote> The only issue I see is that hstore's text format is non-standard, not widely understood and a pain
towork with in applications. You can always write queries against it in Pg and extract normal row sets of key/value
pairs,so it's not a big problem - but I'd want to think about adding a built-in `hstore_to_json` if we were going to
usehstore to manage the data, since json is so much more widely understood by client applications.<br /><br /> Not that
implementing`hstore_to_json` is exactly hard, mind you, as a quick search shows: <a
href="https://gist.github.com/2318757">https://gist.github.com/2318757</a><pre class="moz-signature" cols="72">-- Craig
Ringer                  <a class="moz-txt-link-freetext"
href="http://www.2ndQuadrant.com/">http://www.2ndQuadrant.com/</a>PostgreSQLDevelopment, 24x7 Support, Training &
Services</pre>