[PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7

Hello everyone, With the commit 556f7b7bc18d34ddec45392965c3b3038206bb62, Any plpgsql function that returns scalar value would not be able to use parallelism to evaluate a return statement. It will not be considered for parallel execution because we are passing maxtuples = 2 to exec_run_select fro

Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7

> On Tue, May 20, 2025 at 11:57 AM Dilip Kumar wrote: > > On Mon, May 5, 2025 at 11:19 AM DIPESH DHAMELIYA > wrote: > > > > Hello everyone, > > > > With the commit 556f7b7bc18d34ddec45392965c3b3038206bb62, Any plpgsql > > function that returns scalar

Clarification on DROP OWNED BY command in PG18

Hello everyone,   Starting from commit 98fc31d (PG18 only), there is a new behaviour for DROP OWNED BY command where it deletes entries from pg_auth_members (including entries with ADMIN option). This change can cause a user/role to lose the ability to DROP the role for which DROP OWNED BY was