| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Nicolas Paris <niparisco(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: New Copy Formats - avro/orc/parquet |
| Date: | 2018-02-12 13:55:08 |
| Message-ID: | CABUevExw+qxgE=QrBLjtYZx4qejWVpYsBv+0sU5D8ZvdbQ25mg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Feb 11, 2018 at 11:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > So, I think making COPY extensible would be quite beneficial. I'm
> > however quite doubtful that we want to add core code to handle all of
> > the above. I think we should make the COPY input/output formatting
> > extensible by extensions.
>
> +1. I can't see carrying code for these formats in-core, but I've
> no objection to making it possible for someone else to maintain them.
>
+1. And bonus points if an API can also be defined so such an extension
parsing also becomes useful to file_fdw automatically (or at least
optionally).
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-12 14:09:18 | Re: New Copy Formats - avro/orc/parquet |
| Previous Message | PegoraroF10 | 2018-02-12 13:48:21 | Re: execute block like Firebird does |