| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jens-Wolfhard Schicke-Uffmann <drahflow(at)gmx(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Parameter binding for COPY TO queries |
| Date: | 2025-02-14 20:51:51 |
| Message-ID: | 3901594.1739566311@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2025-02-14 10:06:13 -0500, Tom Lane wrote:
>> None of those arguments apply to the sub-SELECT of a "COPY (query) TO"
>> command, but there's a practical matter of how to get the parameters
>> passed through the COPY to the sub-SELECT without opening Pandora's
>> box for every other kind of utility statement.
> I think there's already precedent - CREATE TABLE AS does accept parameters
> today, and it's a utility command too:
Hmm ... yeah, now that I look, there's more pre-existing plumbing
in ProcessUtility than I remembered. So maybe this wouldn't be too
hard after all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2025-02-14 20:53:25 | Re: Feature Request: Add AES-128-CFB Mode Support to pgcrypto |
| Previous Message | Daniel Gustafsson | 2025-02-14 20:51:37 | Re: New buildfarm animals with FIPS mode enabled |