Re: Best practices for Large import in empty database?

Поиск
Список
Период
Сортировка
От Andy Colson
Тема Re: Best practices for Large import in empty database?
Дата
Msg-id 542C128A.80905@squeakycode.net
обсуждение исходный текст
Ответ на Best practices for Large import in empty database?  (Daniel Begin <jfd553@hotmail.com>)
Список pgsql-general
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




В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Best practices for Large import in empty database?
Следующее
От: jlrando
Дата:
Сообщение: Postgres tcp_keepalive_xxxx parameters.