Re: IMMUTABLE and PARALLEL SAFE function markings - Mailing list pgsql-hackers

From Robert Haas
Subject Re: IMMUTABLE and PARALLEL SAFE function markings
Date
Msg-id CA+TgmobeRXnG3bjczOfKhNbjdsFk0M9iX+ePOZT1Jd1gmXdSMQ@mail.gmail.com
Whole thread Raw
In response to Re: IMMUTABLE and PARALLEL SAFE function markings  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: IMMUTABLE and PARALLEL SAFE function markings  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Re: IMMUTABLE and PARALLEL SAFE function markings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Nov 26, 2018 at 8:49 PM Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
> I'm a bit more concerned by the fact that inlining the function isn't
> affecting the parallel safety of the query - the fact that parallel
> safety is being checked prior to inlining means that if inlining
> *introduces* a parallel hazard, it will go unnoticed?

If a function is marked parallel-safe but internally calls
parallel-restricted or parallel-unsafe functions, it wasn't really
parallel-safe in the first place.  So I think that if inlining
introduces a parallel hazard, the user has mislabeled some functions
and any resulting injury is self-inflicted.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: IMMUTABLE and PARALLEL SAFE function markings
Next
From: Robert Haas
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode