Re: Difference between Bulk Load (Multiple inserts or single inserts) and COPY

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: mayank(dot)l(dot)patel90(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Difference between Bulk Load (Multiple inserts or single inserts) and COPY
Date: 2019-11-19 22:55:44
Message-ID: 41b4852ea43e59969cfefaf37c4578a23000075b.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, 2019-11-19 at 18:55 +0000, PG Doc comments form wrote:
> I experimented with Bulk load and COPY.
> Loading in COPY was very fast.
> However, after COPYing data from a CSV file to PostgreSQL Table. The query
> execution took lot of time for 1 of the first 4 queries.
> Only this slow query was taking so much time, that even if I had used normal
> bulk load, it would have been faster in total.
> Then all other Query executions took equal time as it took while querying a
> table after the Bulk data load method.
>
> So, I want to know the exact reason what's the issue with COPY.
> How exactly they differ? The only thing from the document I could identify
> was row security.
> But it did not mention anything about indexing. Like, in Bulk load, do
> indices(or constraint checks) are created with data loading?
> & in COPY it's done after? so when indices are being created that query
> slows down??
>
> Please reply soon with more details or send a link where I can read it in
> depth.

That cannot be answered without knowing the exact statements and the
table definitions.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2019-11-19 23:05:11 Re: Role membership and DROP
Previous Message Tom Lane 2019-11-19 19:47:16 Re: documentation for WITH RECURSIVE