| From: | Cat <cat(at)zip(dot)com(dot)au> |
|---|---|
| To: | Nicolas Paris <niparisco(at)gmail(dot)com> |
| Cc: | Moreno Andreo <moreno(dot)andreo(at)evolu-s(dot)it>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [SPAM] COPY command & binary format |
| Date: | 2016-05-10 13:06:13 |
| Message-ID: | 20160510130612.GA18865@zip.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 10, 2016 at 01:38:12PM +0200, Nicolas Paris wrote:
> The way I want is :
> csv -> binary -> postgresql
>
> And if possible, transforming csv to binary throught java.
>
> Use case is ETL process.
Not sure what the point would be tbh if the data is already in CSV.
You might aswell submit the CSV to postgres and let it deal with it.
It'll probably be faster. It'll also be more portable. The BINARY
format is what Postgres uses internally (more or less). I had to
look at the source code to figure out how to insert a timestamp
(FYI: Postgres stores timestamps as epoch based off the year 2000 not
1970 amongst other fun things).
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cat | 2016-05-10 13:08:47 | Re: [SPAM] COPY command & binary format |
| Previous Message | Nicolas Paris | 2016-05-10 13:00:55 | Re: [SPAM] COPY command & binary format |