Search Postgresql Archives

Re: Best practices for Large import in empty database?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/1/2014 9:13 AM, Daniel Begin wrote:
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?

Cheers,

Daniel


create index after, as long as you dont need it for uniqueness checking.

then:

begin;
truncate table junk;
copy ...  with freeze;
commit;

Even though the table is empty, the begin,trunc,copy lets PG skip a bunch of extra WAL.

-Andy




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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux