Re: Parallel query: Use TopTransactionContext for ReinitializeParallelDSM()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Parallel query: Use TopTransactionContext for ReinitializeParallelDSM()
Date: 2025-12-16 17:32:22
Message-ID: CA+TgmoaA6F-cev5f5J9HVCU_iAKDgU00kYxgKif2AAvmpTt9Sg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 10, 2025 at 3:03 AM Jeevan Chalke
<jeevan(dot)chalke(at)enterprisedb(dot)com> wrote:
> Although I was unable to reproduce the reported issue, a review of the code flow confirms that to maintain consistency with all other Parallel Query memory allocations, the context should be switched to TopTransactionContext. This change appears correct and serves as a necessary safeguard to prevent potential future race conditions.

Committed and back-patched.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-12-16 17:40:44 Re: [oauth] Stabilize the libpq-oauth ABI (and allow alternative implementations?)
Previous Message Melanie Plageman 2025-12-16 17:16:55 Re: Adding vacuum test case of setting the VM when heap page is unmodified