Re: json api WIP patch - Mailing list pgsql-hackers

From james
Subject Re: json api WIP patch
Date
Msg-id 50EBC09E.8070303@mansionfamily.plus.com
Whole thread Raw
In response to Re: json api WIP patch  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: json api WIP patch
List pgsql-hackers
> The processing functions have been extended to provide populate_record() and populate_recordset() functions.The
latterin particular could be useful in decomposing a piece of json representing an array of flat objects (a fairly
commonpattern) into a set of Postgres records in a single pass.
 

So this would allow an 'insert into ... select ... from 
<unpack-the-JSON>(...)'?

I had been wondering how to do such an insertion efficiently in the 
context of SPI, but it seems that there is no SPI_copy equiv that would 
allow a query parse and plan to be avoided.

Is this mechanism likely to be as fast as we can get at the moment in 
contexts where copy is not feasible?




pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Set visibility map bit after HOT prune
Next
From: Kohei KaiGai
Date:
Subject: Re: recent ALTER whatever .. SET SCHEMA refactoring