hstore parser about plv8 HOT 5 CLOSED

Yeah, hstore is always a headache to PLs and I wish it were a built-in.  I 
don't know about it so much ATM but Peter and others are developing 
"transformation" of type conversion between database and PLs. I don't 
personally like to take special treatment for hstore which is not a built-in.  
If we do it, what about type-X and type-Y?

The real problem is that since hstore isn't built in it doesn't have a fixed 
type Oid. At the developers conference in May I suggested we have a registry of 
known types so that we could in future deal in confidence with non-builtin 
types, but there is nothing there yet. Until there is I don't see any realistic 
way of dealing with this. I would suggest you handle this in user code. 

proposed enhancements for 9.3 include an hstore function to emit json. so the 
workaround in this case would be to pass an hstore argument wrapped in this 
function, or call it from inside plv8.

So no fix needed here?

As per comments, no fix needed.