Re: pgsql: Allow page lock to conflict among parallel group members. - Mailing list pgsql-committers

From Amit Kapila
Subject Re: pgsql: Allow page lock to conflict among parallel group members.
Date
Msg-id CAA4eK1JvupHQ9Ud+0-mfY4XgkMz=Oq2Q1XtgFa_RdVvVyUAsCA@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Allow page lock to conflict among parallel group members.  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
On Sun, Mar 22, 2020 at 5:57 AM Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2020-03-21 03:27:07 +0000, Amit Kapila wrote:
> > Currently, the parallel mode is strictly read-only, but after this patch
> > we have the infrastructure to allow parallel inserts and parallel copy.
>
> Minor nit: I don't think this gets to fully having the infrastructure
> for that. It just removes one roadblock. Or am I missing something here?
>

AFAIU, after this, we don't have more roadblocks for parallel inserts,
copy or similar operations where workers will be able to perform
insert operation, surely there is much more work required to make
those actually parallel.  The other opportunities this opens up are
allowing multiple workers for one large index cleanups and heap pass
in a parallel vacuum.  Do you see any other fundamental problems that
need to be solved for parallel inserts?

Having said that, we still have some problems to solve to make updates
or deletes parallel.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: Allow page lock to conflict among parallel group members.
Next
From: Noah Misch
Date:
Subject: pgsql: Revert "Skip WAL for new relfilenodes, under wal_level=minimal."