| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | James Sewell <james(dot)sewell(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY table FROM STDIN via SPI |
| Date: | 2023-07-12 18:18:41 |
| Message-ID: | d30df590-4858-5e84-7d12-3cbef3aa672f@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/11/23 22:52, James Sewell wrote:
>
> No. It'd be a wire protocol break, and even if it weren't I would not
> expect many clients to be able to deal with it. They're in the middle
> of a query cycle (for the SELECT or CALL that got you into SPI), and
> suddenly the backend asks for COPY data? What are they supposed to
> send, or where are they supposed to put it for the COPY-out case?
> There's just not provision for nesting protocol operations like that.
>
>
> What about running a COPY directly from C - is that possible?
https://www.postgresql.org/docs/current/libpq-copy.html
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chap | 2023-07-12 18:43:21 | Re: COPY table FROM STDIN via SPI |
| Previous Message | Gurjeet Singh | 2023-07-12 17:47:56 | Re: Better help output for pgbench -I init_steps |