| From: | Sutou Kouhei <kou(at)clear-code(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Is it acceptable making COPY format extendable? |
| Date: | 2024-04-23 05:14:55 |
| Message-ID: | 20240423.141455.749489809169803531.kou@clear-code.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Thanks,
--
kou
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-04-23 05:42:08 | Re: Direct SSL connection with ALPN and HBA rules |
| Previous Message | Michael Paquier | 2024-04-23 05:05:03 | Re: Support a wildcard in backtrace_functions |