|From:||Andrew Dunstan <andrew(at)dunslane(dot)net>|
|Cc:||Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: json api WIP patch|
|Views:||Raw Message | Whole Thread | Download mbox|
On 01/08/2013 03:07 PM, james wrote:
> Yes - but I don't think I can use COPY from a stored proc context can
> I? If I could use binary COPY from a stored proc that has received a
> binary param and unpacked to the data, it would be handy.
You can use COPY from a stored procedure, but only to and from files.
> If SPI provided a way to perform a copy to a temp table and then some
> callback on an iterator that yields rows to it, that would do the
> trick I guess.
SPI is useful, but it's certainly possible to avoid its use. After all,
that what almost the whole backend does, including the COPY code. Of
course, it's a lot harder to write that way, which is part of why SPI
exists. Efficiency has its price.
|Next Message||Tom Lane||2013-01-08 20:27:23||Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it|
|Previous Message||Andrew Dunstan||2013-01-08 20:22:13||Re: json api WIP patch|