Re: Unexpectedly exposed COPY option: convert_selectively
KAZAR Ayoub <ma_kazar@esi.dz>
From: KAZAR Ayoub <ma_kazar@esi.dz>
To: Sugamoto Shinya <shinya34892@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2026-02-20T15:53:14Z
Lists: 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Skip text->binary conversion of unnecessary columns in contrib/file_fdw.
- a36088bcfae8 9.3.0 cited