| From: | Nicolas Paris <niparisco(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: New Copy Formats - avro/orc/parquet |
| Date: | 2018-02-10 15:30:11 |
| Message-ID: | 20180210153011.o2w3tdriqmwvahph@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > I d'found useful to be able to import/export from postgres to those modern data
> > formats:
> > - avro (c writer=https://avro.apache.org/docs/1.8.2/api/c/index.html)
> > - parquet (c++ writer=https://github.com/apache/parquet-cpp)
> > - orc (all writers=https://github.com/apache/orc)
> >
> > Something like :
> > COPY table TO STDOUT ORC;
> >
> > Would be lovely.
> >
> > This would greatly enhance how postgres integrates in big-data ecosystem.
> >
> > Any thought ?
>
> https://www.postgresql.org/docs/10/static/sql-copy.html
>
> "PROGRAM
>
> A command to execute. In COPY FROM, the input is read from standard
> output of the command, and in COPY TO, the output is written to the standard
> input of the command.
>
> Note that the command is invoked by the shell, so if you need to pass
> any arguments to shell command that come from an untrusted source, you must
> be careful to strip or escape any special characters that might have a
> special meaning for the shell. For security reasons, it is best to use a
> fixed command string, or at least avoid passing any user input in it.
> "
>
PROGRAM would involve overhead of transforming data from CSV or BINARY
to AVRO for example.
Here, I am talking about native format exports/imports for performance
considerations.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-02-10 15:38:10 | Re: New Copy Formats - avro/orc/parquet |
| Previous Message | Adrian Klaver | 2018-02-10 15:25:18 | Re: New Copy Formats - avro/orc/parquet |