Re: Unexpectedly exposed COPY option: convert_selectively - Mailing list pgsql-hackers

From KAZAR Ayoub
Subject Re: Unexpectedly exposed COPY option: convert_selectively
Date
Msg-id CA+K2RukpSoSXBOOxoQ9hOmKYx3_SeG2qyT4-qjbrt+z-Yspn=g@mail.gmail.com
Whole thread
In response to Unexpectedly exposed COPY option: convert_selectively  (Sugamoto Shinya <shinya34892@gmail.com>)
List pgsql-hackers
Hello,

On Fri, Feb 20, 2026 at 3:19 AM Sugamoto Shinya <shinya34892@gmail.com> wrote:
My preference is Option 1, since it’s the simplest change and, as far
as I know, there are no user-facing issues today. Option 2 would be a
backward-incompatible change (even if undocumented). Option 3 would
require additional work to make it a supported and documented feature,
and I’m not aware of a clear demand/use case yet.
For option 3, i don't see a use case other than one would want to have a different option of selectively picking input fields to map them to a subset of table columns, this is far from being similar to convert_selectively implementation (as the first is more complex), so option 1 seems like it.
Regards,
Shinya Sugamoto

Regards,
Ayoub

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: ecdh support causes unnecessary roundtrips
Next
From: Bertrand Drouvot
Date:
Subject: Re: Flush some statistics within running transactions