Re: [HACKERS] Creating a DSA area to provide work space for parallel execution - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Creating a DSA area to provide work space for parallel execution
Date
Msg-id CA+TgmoazEK1KxQSOQZ10N=F1pH2WOav8d4p_shZ-r+cbgqjUYA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Creating a DSA area to provide work space for parallel execution  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On Mon, Dec 19, 2016 at 6:35 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Tue, Dec 20, 2016 at 11:12 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, Dec 1, 2016 at 6:35 AM, Thomas Munro
>> <thomas.munro@enterprisedb.com> wrote:
>>> On Sat, Nov 26, 2016 at 1:55 AM, Thomas Munro
>>> <thomas.munro@enterprisedb.com> wrote:
>>>> Here's a new version to apply on top of dsa-v7.patch.
>>>
>>> Here's a version to go with dsa-v8.patch.
>>
>> All right, so I've committed this, but not before (1) renaming some
>> things that you added, (2) adding documentation for the new LWLock
>> tranche, (3) not creating the DSA in the "simulated DSM using
>> backend-private memory" case, and (4) some cosmetic tweaks.
>
> Thanks!  Hmm, so now in rare circumstances we can finish up running
> ExecXXXInitializeDSM, but later have estate->es_query_dsa == NULL.
> This is something to be careful about.

Yes.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical Replication WIP
Next
From: Robert Haas
Date:
Subject: Re: pg_authid.rolpassword format (was Re: [HACKERS] Passwordidentifiers, protocol aging and SCRAM protocol)