Re: COPY table FROM STDIN via SPI

From: James Sewell <james(dot)sewell(at)gmail(dot)com>
To: 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 02:52:37
Message-ID: CAJe2zgPPs-6mHDaGG29YEkQsQ8mkokjptOLpqFKoFwfmxukD6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2023-07-12 02:57:44 Re: The same 2PC data maybe recovered twice
Previous Message David Rowley 2023-07-12 02:50:15 Re: unrecognized node type while displaying a Path due to dangling pointer