Re: [bug?] Missed parallel safety checks, and wrong parallel safety - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [bug?] Missed parallel safety checks, and wrong parallel safety
Date
Msg-id CA+TgmoYoisfDs4yw5K0JkoDmd7y60R16XvC+-uzHHFgvCD9-tA@mail.gmail.com
Whole thread Raw
In response to Re: [bug?] Missed parallel safety checks, and wrong parallel safety  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [bug?] Missed parallel safety checks, and wrong parallel safety  (Greg Nancarrow <gregn4422@gmail.com>)
List pgsql-hackers
On Fri, Apr 23, 2021 at 10:53 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> Isn't parallel safety also the C code property?

In my opinion, yes.

> So, isn't it better to disallow changing parallel
> safety for built-in functions?

Superusers can do a lot of DML operations on the system catalogs that
are manifestly unsafe. I think we should really consider locking that
down somehow, but I doubt it makes sense to treat this case separately
from all the others. What do you think will happen if you change
proargtypes?

> Also, if the strict property of built-in functions is fixed
> internally, why we allow users to change it and is that of any help?

One real application of allowing these sorts of changes is letting
users correct things that were done wrong originally without waiting
for a new major release.

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



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: MaxOffsetNumber for Table AMs
Next
From: Pavel Stehule
Date:
Subject: Re: few ideas for pgbench