Search Postgresql Archives

Re: COPY threads

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

Subject: Re: COPY threads
From: Andres Freund <andres@xxxxxxxxxxx>
Date: Wed, 10 Oct 2018 14:07:29 -0700
Cc: Christopher Browne <cbbrowne@xxxxxxxxx>, laurenz.albe@xxxxxxxxxxx, Rob Sargent <robjsargent@xxxxxxxxx>, PostgreSQL Mailing Lists <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <7FCA0163-130B-474D-BE00-3BB5D2E0EC89@aol.com>
References: <065f5e56-5b25-0ce2-e20b-4305f71b2301@gmail.com> <d198d930f6c764c8c8667023fc2de333e02ddf46.camel@cybertec.at> <20181010192440.cdxues44gcvx2sbi@alap3.anarazel.de> <B732777C-37FC-484A-A84B-6A7C20D4D2B5@aol.com> <CAFNqd5UMtCNiHsMLkirywcZC=QOE=ThEy1ABn6-+rVC5j73g3Q@mail.gmail.com> <7FCA0163-130B-474D-BE00-3BB5D2E0EC89@aol.com>

Hi,

On 2018-10-10 17:02:59 -0400, Ravi Krishna wrote:
> I am talking about pg_restore which is COPY FROM, which takes exclusive lock on the table
> while the data is loaded into the table.

pg_restore doesn't take locks on the table for the COPY, it does so
because creating the table takes an exclusive lock.

Greetings,

Andres Freund

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

Follow-Ups:
- Re: COPY threads
  - From: Ravi Krishna

References:
- COPY threads
  - From: Rob Sargent
- Re: COPY threads
  - From: Laurenz Albe
- Re: COPY threads
  - From: Andres Freund
- Re: COPY threads
  - From: Ravi Krishna
- Re: COPY threads
  - From: Christopher Browne
- Re: COPY threads
  - From: Ravi Krishna

Prev by Date: Re: COPY threads
Next by Date: Re: COPY threads
Previous by thread: Re: COPY threads
Next by thread: Re: COPY threads
Index(es):
- Date
- Thread

[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