| From: | Sutou Kouhei <kou(at)clear-code(dot)com> |
|---|---|
| To: | zhjwpku(at)gmail(dot)com |
| Cc: | sawada(dot)mshk(at)gmail(dot)com, andrew(at)dunslane(dot)net, michael(at)paquier(dot)xyz, nathandbossart(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Date: | 2024-01-26 08:55:11 |
| Message-ID: | 20240126.175511.2017689682651924758.kou@clear-code.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
In <CAEG8a3KhS6s1XQgDSvc8vFTb4GkhBmS8TxOoVSDPFX+MPExxxQ(at)mail(dot)gmail(dot)com>
"Re: Make COPY format extendable: Extract COPY TO format implementations" on Fri, 26 Jan 2024 16:41:50 +0800,
Junwang Zhao <zhjwpku(at)gmail(dot)com> wrote:
> CopyToProcessOption()/CopyFromProcessOption() can only handle
> single option, and store the options in the opaque field, but it can not
> check the relation of two options, for example, considering json format,
> the `header` option can not be handled by these two functions.
>
> I want to find a way when the user specifies the header option, customer
> handler can error out.
Ah, you want to use a built-in option (such as "header")
value from a custom handler, right? Hmm, it may be better
that we call CopyToProcessOption()/CopyFromProcessOption()
for all options including built-in options.
Thanks,
--
kou
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2024-01-26 09:02:23 | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Previous Message | Sutou Kouhei | 2024-01-26 08:49:47 | Re: Make COPY format extendable: Extract COPY TO format implementations |