From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Sutou Kouhei <kou(at)clear-code(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Is it acceptable making COPY format extendable? |
Date: | 2024-04-24 07:57:38 |
Message-ID: | 02cccd36-3083-4a50-aae4-f957e96fb7c3@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 23.04.24 07:14, Sutou Kouhei wrote:
> Hi,
>
> I'm proposing a patch that making COPY format extendable:
> https://www.postgresql.org/message-id/20231204.153548.2126325458835528809.kou%40clear-code.com
> https://commitfest.postgresql.org/48/4681/
>
> It's based on the discussion at:
> https://www.postgresql.org/message-id/flat/3741749(dot)1655952719(at)sss(dot)pgh(dot)pa(dot)us#2bb7af4a3d2c7669f9a49808d777a20d
>
>>>> IIUC, you want extensibility in FORMAT argument to COPY command
>>>> https://www.postgresql.org/docs/current/sql-copy.html. Where the
>>>> format is pluggable. That seems useful.
>>
>>> Agreed.
>>
>> Ditto.
>
> But my proposal stalled. It it acceptable the feature
> request that making COPY format extendable? If it's not
> acceptable, what are blockers? Performance?
I think that thread is getting an adequate amount of attention. Of
course, you can always wish for more, but "stalled" looks very different.
Let's not start a new thread here to discuss the merits of the other
thread; that discussion belongs there.
From | Date | Subject | |
---|---|---|---|
Next Message | Nazir Bilal Yavuz | 2024-04-24 08:37:21 | Re: Show WAL write and fsync stats in pg_stat_io |
Previous Message | Heikki Linnakangas | 2024-04-24 07:51:07 | Re: Feature request: schema diff tool |