| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Mahi Gurram <teckymahi(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Regarding Postgres Dynamic Shared Memory (DSA) |
| Date: | 2017-05-26 21:06:56 |
| Message-ID: | CAA4eK1KboAiTjRge9B3aEE2U55=hUeb4NFX20nK-Wa4JppAt5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 24, 2017 at 11:39 AM, Mahi Gurram <teckymahi(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kha Nguyen | 2017-05-26 21:09:37 | Re: Extra Vietnamese unaccent rules |
| Previous Message | Peter Eisentraut | 2017-05-26 21:05:37 | Re: Create subscription with `create_slot=false` and incorrect slot name |