Re: postgres import

From: "Tomi NA" <hefest(at)gmail(dot)com>
To: "Alban Hertroys" <alban(at)magproductions(dot)nl>
Cc: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>, "Antonios Katsikadamos *EXTERN*" <antonioskatsikadamos(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: postgres import
Date: 2006-11-01 10:41:13
Message-ID: d487eb8e0611010241j7731ba3k269521ea0e208149@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2006/11/1, Alban Hertroys <alban(at)magproductions(dot)nl>:
> Tomi NA wrote:
> > 2006/10/31, Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>:
> >> You feed it to the command line interface psql.
> >>
> >> Example:
> >> psql -h host -p port -d database -U user <dump.sql
> >
> > It's a good enough solution in most cases, but when the rowcount
> > starts to skyrocket, it simply doesn't seem to cut it (at least I
> > couldn't make it to). To load 1,5M rows (~230MB of INSERT statements),
>
> INSERT statements? You dumped with the -d flag, didn't you? Otherwise
> you'd have seen COPY statements instead, which are much faster (and of
> which much fewer are necessary, usually).

No I didn't, actually. :) The data was never in the database in the
first place: it was generated from a different source. True, it was
generated as a CSV file which I converted into INSERT statements, but
conversion between the two is not a problem (given 1.5GB of RAM).

t.n.a.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2006-11-01 10:41:43 Re: Encoding, Unicode, locales, etc.
Previous Message Bobby Gontarski 2006-11-01 09:58:21 blocking mode