Re: Best practices for Large import in empty database? - Mailing list pgsql-general

From Daniel Begin
Subject Re: Best practices for Large import in empty database?
Date
Msg-id COL129-DS1707EE8AE25464429C0B2D94B80@phx.gbl
Whole thread Raw
In response to Re: Best practices for Large import in empty database?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Oups, right to the point! Thanks...

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

Daniel Begin <jfd553@hotmail.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@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



pgsql-general by date:

Previous
From: jlrando
Date:
Subject: Postgres tcp_keepalive_xxxx parameters.
Next
From: Tom Lane
Date:
Subject: Re: Postgres tcp_keepalive_xxxx parameters.