public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jim Vanns <[email protected]>
To: pgsql-general <[email protected]>
Subject: Parallel workers via functions?
Date: Mon, 27 Jan 2025 18:08:53 +0000
Message-ID: <CAH7vdhPr9BJ2TjbVU0RepN92eUFmWorukAGEyhBqpx8gF67xdQ@mail.gmail.com> (raw)

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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: Parallel workers via functions?
  In-Reply-To: <CAH7vdhPr9BJ2TjbVU0RepN92eUFmWorukAGEyhBqpx8gF67xdQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox