| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | knizhnik <knizhnik(at)garret(dot)ru> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| Date: | 2014-01-09 19:36:48 |
| Message-ID: | CAA4eK1LMiSvf1WALkWMUL5b+86DpgeSgikAiZb0DVkuW8eJymw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-announce pgsql-hackers |
On Fri, Jan 10, 2014 at 1:00 AM, knizhnik <knizhnik(at)garret(dot)ru> wrote:
> On 01/09/2014 11:09 PM, Amit Kapila wrote:
>>
>>
>> Using DuplicateHandle(), we can make segment stick for Postmaster
>> lifetime. I have used below test (used dsm_demo module) to verify:
>
> As far as I understand DuplicateHandle() should really do the trick: protect
> segment from deallocation.
> But should postmaster be somehow notified about this handle?
> For example, if we really wants to delete this segment (drop extension), we
> should somehow make Postmaster to close this handle.
> How it can be done?
I think we need to use some form of IPC to communicate it to Postmaster.
I could not think of any other way atm.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | knizhnik | 2014-01-09 19:39:36 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| Previous Message | knizhnik | 2014-01-09 19:30:59 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | knizhnik | 2014-01-09 19:39:36 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| Previous Message | knizhnik | 2014-01-09 19:30:59 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |