| From: | Nicolas Paris <niparisco(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: New Copy Formats - avro/orc/parquet |
| Date: | 2018-02-11 20:57:35 |
| Message-ID: | 20180211205735.nt6auxazit42qmcs@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 11 févr. 2018 à 21:53, Andres Freund écrivait :
> On 2018-02-11 21:41:26 +0100, Nicolas Paris wrote:
> > I have also the storage and network transfers overhead in mind:
> > All those new formats are compressed; this is not true for current
> > postgres BINARY format and obviously text based format. By experience,
> > the binary format is 10 to 30% larger than the text one. On the
> > contrary, an ORC file can be up to 10 times smaller than a text base
> > format.
>
> That seems largely irrelevant when arguing about using PROGRAM though,
> right?
>
Indeed those storage and network transfers are only considered versus
CSV/BINARY format. No link with PROGRAM aspect.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-02-11 21:12:35 | Re: New Copy Formats - avro/orc/parquet |
| Previous Message | Andres Freund | 2018-02-11 20:53:46 | Re: New Copy Formats - avro/orc/parquet |