Re: [HACKERS] Regarding Postgres Dynamic Shared Memory (DSA) - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [HACKERS] Regarding Postgres Dynamic Shared Memory (DSA)
Date
Msg-id CAA4eK1KboAiTjRge9B3aEE2U55=hUeb4NFX20nK-Wa4JppAt5g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Regarding Postgres Dynamic Shared Memory (DSA)  (Mahi Gurram <teckymahi@gmail.com>)
List pgsql-hackers
On Wed, May 24, 2017 at 11:39 AM, Mahi Gurram <teckymahi@gmail.com> wrote:
> One solution that is striking me is....
> 1. I'll create one background worker and will initialise DSA in it.
> 2. If there are any callbacks available for client open/close connections,
> i'll attach/detach to the DSA in those callbacks.
>
> But i'm not sure there are such callbacks available. If such callbacks
> exists in postgres and you guys know please help me out with that.
>

We do share DSA handle, planned statement, params etc from master
backend with workers.  See ExecInitParallelPlan that might help you in
your work.


-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Create subscription with `create_slot=false` andincorrect slot name
Next
From: Kha Nguyen
Date:
Subject: Re: [HACKERS] Extra Vietnamese unaccent rules