Re: Best practices for Large import in empty database?

From: Daniel Begin <jfd553(at)hotmail(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best practices for Large import in empty database?
Date: 2014-10-01 15:00:27
Message-ID: COL129-DS1707EE8AE25464429C0B2D94B80@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Oups, right to the point! Thanks...

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: October-01-14 10:38
To: Daniel Begin
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Best practices for Large import in empty database?

Daniel Begin <jfd553(at)hotmail(dot)com> writes:
> I am about to feed an empty database with a large import of data (the
> size of csv files is about 500 GB). Tables are created but I haven't
> added any constraints or indexes yet. I wonder whether the best
> practice is to add them before or after the import. Are there other
> good practices that would ease the import process?

http://www.postgresql.org/docs/9.3/static/populate.html

regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-10-01 15:04:06 Re: Postgres tcp_keepalive_xxxx parameters.
Previous Message jlrando 2014-10-01 14:57:40 Postgres tcp_keepalive_xxxx parameters.