Re: COPY threads

From: Ravi Krishna <srkrishna1(at)aol(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Rob Sargent <robjsargent(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: COPY threads
Date: 2018-10-10 20:21:54
Message-ID: B732777C-37FC-484A-A84B-6A7C20D4D2B5@aol.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> You obviously can just copy the data into postgres over multiple
> connections if you need to speed COPY up. But that requires splitting up
> the data on the clientside.
>

You obviously are referring to multiple connections running COPY on different tables, right? Like what pg_restore does with -j option.
Doesn't copy take an exclusive lock on the table which makes it incompatible with parallelization.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christopher Browne 2018-10-10 20:32:07 Re: COPY threads
Previous Message Rob Sargent 2018-10-10 19:41:37 Re: COPY threads