Hi all,
Sorry for the late reply.
I could handle the pb by transforming my function check ( with an exception ) by a simple sql immutable function.
Function before
CREATE OR REPLACE FUNCTION test_id(ltree[]) |
|
FOR id IN SELECT unnest($1) LOOP |
|
WHEN OTHERS THEN RETURN FALSE; |
|
LANGUAGE plpgsql VOLATILE;
AFTER
CREATE OR REPLACE FUNCTION test_Id(ltree[]) |
|
LANGUAGE sql IMMUTABLE STRICT; |
|
Hello, how could I relax the subtransaction restriction, I used the Parallel Unsafe option, but still have the same issue.
Rgds.
Hi,
On 2018-06-29 20:37:23 +0200, Tomas Vondra wrote:
> My guess is that it's a PL/pgSQL function with an EXCEPTION block, and
> there's no easy way to "fix" that.
Obviously not going to immediately help the OP, but I do think we should
be able to relax the subtransaction restriction around parallelism
without too much work. Can't allow xids to be assigned, but that's
probably ok for a lot of exception handling cases.
Greetings,
Andres Freund