Re: IO wait events for COPY FROM/TO PROGRAM or file - Mailing list pgsql-hackers

From Nikolay Samokhvalov
Subject Re: IO wait events for COPY FROM/TO PROGRAM or file
Date
Msg-id CAM527d8uWd3dowhF5yEfpzqGw4zFM5nT7wxR2ptnJkEUVB3=iA@mail.gmail.com
Whole thread Raw
In response to Re: IO wait events for COPY FROM/TO PROGRAM or file  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Sun, Jan 11, 2026 at 02:22 Michael Paquier <michael@paquier.xyz> wrote:
On Thu, Jan 08, 2026 at 09:22:26PM -0600, Sami Imseih wrote:
> I don't see any issue with this approach for fwrite().

Please feel free to discard my comment, then :)

> Another comment. Wouldn't be better to use "COPY FROM" and "COPY TO" in the
> names to make it more obvious they are related to the COPY command?

Yeah, we had better do that.  That's slightly cleaner for the user if
they mix both COPY types at the same time, not requiring a mental
mapping that FROM is a read and TO is a write.


v2 attached with the rename per feedback: COPY_DATA_READ/WRITE →
COPY_FROM_READ/COPY_TO_WRITE.

Given how small this patch is, any chance it could still make PG19?
Attachment

pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: Allow GUC settings in CREATE SUBSCRIPTION CONNECTION to take effect
Next
From: Lukas Fittl
Date:
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?