| From: | "Sanaba, Bilva" <bilvas(at)amazon(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Adding Support for Copy callback functionality on COPY TO api |
| Date: | 2020-07-01 21:41:12 |
| Message-ID: | 253C21D1-FCEB-41D9-A2AF-E6517015B7D7@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers,
Currently, the COPY TO api does not support callback functions, while the COPY FROM api does. The COPY TO code does, however, include placeholders for supporting callbacks in the future.
Rounding out the support of callback functions to both could be very beneficial for extension development. In particular, supporting callbacks for COPY TO will allow developers to utilize the preexisting command in order to create tools that give users more support for moving data for storage, backup, analytics, etc.
We are aiming to get the support in core PostgreSQL and add COPY TO callback support in the next commitfest. The attached patch contains a change to COPY TO api to support callbacks.
Best,
Bilva
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Support-COPY-TO-callback-functions.patch | application/octet-stream | 4.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2020-07-01 21:43:37 | Re: pg_read_file() with virtual files returns empty string |
| Previous Message | Bruce Momjian | 2020-07-01 21:25:26 | Re: Remove Deprecated Exclusive Backup Mode |