Re: Allow parallel plan for referential integrity checks? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Allow parallel plan for referential integrity checks?
Date
Msg-id CA+TgmobLe8hTPJJ5fnLn+Hw0YnUGRr85ROD5M2zrkVKhBCPkyA@mail.gmail.com
Whole thread Raw
In response to Allow parallel plan for referential integrity checks?  (Frédéric Yhuel <frederic.yhuel@dalibo.com>)
Responses Re: Allow parallel plan for referential integrity checks?  (Frédéric Yhuel <frederic.yhuel@dalibo.com>)
List pgsql-hackers
On Mon, Feb 7, 2022 at 5:26 AM Frédéric Yhuel <frederic.yhuel@dalibo.com> wrote:
> I noticed that referential integrity checks aren't currently
> parallelized. Is it on purpose?

It's not 100% clear to me that it is safe. But on the other hand, it's
also not 100% clear to me that it is unsafe.

Generally, I only added CURSOR_OPT_PARALLEL_OK in places where I was
confident that nothing bad would happen, and this wasn't one of those
places. It's something of a nested-query environment -- your criterion
#6. How do we know that the surrounding query isn't already parallel?
Perhaps because it must be DML, but I think it must be more important
to support parallel DML than to support this.

I'm not sure what the right thing to do here is, but I think it would
be good if your patch included a test case.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: sockaddr_un.sun_len vs. reality
Next
From: Ashutosh Sharma
Date:
Subject: Re: Make mesage at end-of-recovery less scary.