RE: Parallel Apply - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Parallel Apply
Date
Msg-id OSCPR01MB14966B464C274665B21FF4320F5B0A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Parallel Apply  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses RE: Parallel Apply
List pgsql-hackers
Dear Hackers,

Here is a rebased version.
Since the parallel worker's bug has been fixed, the patch is not attached anymore.

0006 contains changes to handle the case that user-defined triggers are not
immutable. Some triggers may change their behaviors based on the number of tuples
and other internal states. To keep the result consistent with the non-parallel
case, parallel workers wait to apply changes till the previous transaction is
committed if the target relation has such triggers.
Note that we assume CHECK constraints are immutable, so they are not checked.
I think it is a reasonable assumption because it has already been described in
the doc [1].
(This does not contain tests yet)

0007 contains changes for track dependencies by local indexes. It was mostly the
same as v5-0008. Since I cannot find a reasonable way to compute a hash for
expression indexes, these indexes are no longer used for tracking. Instead, the
parallel worker waits to apply changes till the previous transaction is
committed if the target relation has such indexes.


[1]: https://www.postgresql.org/docs/current/ddl-constraints.html

Best regards,
Hayato Kuroda
FUJITSU LIMITED


Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Switch buffile.c/h to use pgoff_t
Next
From: Chao Li
Date:
Subject: Re: [Patch]Add tab completion for DELETE ... USING