| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Make COPY extendable in order to support Parquet and other formats |
| Date: | 2022-06-22 11:29:16 |
| Message-ID: | CAExHW5t2Q4+dgne6b0kj==OWmVNK35Xu_p6oUNZwxS2UkKfvMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 21, 2022 at 3:26 PM Aleksander Alekseev
<aleksander(at)timescale(dot)com> wrote:
>
> In other words, personally I'm unaware of use cases when somebody
> needs a complete read/write FDW or TableAM implementation for formats
> like Parquet, ORC, etc. Also to my knowledge they are not particularly
> optimized for this.
>
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.
Another option is to dump the data in csv format but use external
utility to convert csv to parquet or whatever other format is. I
understand that that's not going to be as efficient as dumping
directly in the desired format.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2022-06-22 11:32:31 | Re: Replica Identity check of partition table on subscriber |
| Previous Message | Peter Eisentraut | 2022-06-22 11:12:21 | Unify DLSUFFIX on Darwin |