From: | Jim Vanns <jvanns(at)ilm(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Parallel workers via functions? |
Date: | 2025-01-27 18:08:53 |
Message-ID: | CAH7vdhPr9BJ2TjbVU0RepN92eUFmWorukAGEyhBqpx8gF67xdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Apologies for the rushed question ...
If I have a function that is marked 'stable parallel safe' and returns
a table, can a calling function or procedure (marked volatile parallel
unsafe) still take advantage of the parallel workers from the first
function - as the data source. I.e.
func_a(); // selects, returns table, parallel safe
func_b() {
insert into foo
select * from func_a(); // Will func_a still execute parallel
workers to fetch the data?
}
Or even if func_b() uses 'create temporary table as select * from
func_a()' and then insert?
I ask because when I simply call func_a() from a psql shell, I see the
parallel workers run and everything is nice and swift. But when called
from a data-modifying function like func_b(), no workers are spawned
:( Even from the read-part of the code.
Are there differences in functions vs. stored procedures that might
affect the behaviour of the planner to disregard workers?
Cheers
Jim
--
Jim Vanns
Principal Production Engineer
Industrial Light & Magic, London
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2025-01-27 20:38:39 | Re: Disabling vacuum truncate for autovacuum |
Previous Message | Laurenz Albe | 2025-01-27 09:55:34 | Re: Disabling vacuum truncate for autovacuum |