Re: [Proposal] Adding TRIM_SPACE option to COPY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: 河田達也 <kawatatatsuya0913(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Proposal] Adding TRIM_SPACE option to COPY
Date: 2025-11-25 05:16:55
Message-ID: 1132608.1764047815@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> On Tue, Nov 25, 2025 at 1:18 AM 河田達也 <kawatatatsuya0913(at)gmail(dot)com> wrote:
>> I'd like to propose adding a new option, TRIM_SPACE, to the COPY command.

> I like this idea in general.

I'm kind of down on it, because it's inevitably going to add
processing overhead to every COPY operation whether the feature
is used or not. I don't find it likely to be sufficiently
useful to justify that universal cost.

COPY is not a general-purpose filter or ETL tool, and we try
to make it one at our peril.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-11-25 05:40:33 Re: Remove useless casting to the same type
Previous Message Myles Lewis 2025-11-25 05:01:56 [PATCH] Add native PIVOT syntax for SQL Server/Oracle compatibility