On 19.04.22 16:39, Tom Lane wrote:
> Maybe we should fix JsonPathSpec to be less creative while we
> still can? It's not real clear to me why that typedef even exists,
> rather than using a String node, or just a plain char * field.
Yeah, let's get rid of it and use char *.
I see in JsonCommon a pathspec is converted to a String node, so it's
not like JsonPathSpec is some kind of universal representation of the
thing anyway.