Re: Bulk Insert into PostgreSQL
| От | Don Seiler |
|---|---|
| Тема | Re: Bulk Insert into PostgreSQL |
| Дата | |
| Msg-id | CAHJZqBAjGNHT3ZyvkoU_ED6y5YQBVcVSzmqG+Hctj2k33LX3Og@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Bulk Insert into PostgreSQL (Pavel Stehule <pavel.stehule@gmail.com>) |
| Ответы |
Re: Bulk Insert into PostgreSQL
|
| Список | pgsql-hackers |
On Wed, Jun 27, 2018 at 6:25 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
Other parameters are set to default value. Moreover, I have specified the primary key constraint during table creation. This is the only possible index being created before data loading and I am sure there are no other indexes apart from the primary key column(s).
When doing initial bulk data loads, I would suggest not applying ANY constraints or indexes on the table until after the data is loaded. Especially unique constraints/indexes, those will slow things down A LOT.
The main factor is using COPY instead INSERTs.
Don Seiler
www.seiler.us
www.seiler.us
В списке pgsql-hackers по дате отправления: