From: | james <james(at)mansionfamily(dot)plus(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Константин Книжник <knizhnik(at)garret(dot)ru>, 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-06 20:59:13 |
Message-ID: | 52CB1921.8000505@mansionfamily.plus.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-hackers |
On 06/01/2014 03:14, Robert Haas wrote:
> That's up to the application. After calling dsm_create(), you call
> dsm_segment_handle() to get the 32-bit integer handle for that
> segment. Then you have to get that to the other process(es) somehow.
> If you're trying to share a handle with a background worker, you can
> stuff it in bgw_main_arg. Otherwise, you'll probably need to store it
> in the main shared memory segment, or a file, or whatever.
Well, that works for sysv shm, sure. But I was interested (possibly
from Konstantin)
how the handle transfer takes place at the moment, particularly if it is
possible
to create additional segments dynamically. I haven't looked at the
extension at all.
From | Date | Subject | |
---|---|---|---|
Next Message | james | 2014-01-06 21:04:09 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
Previous Message | David Fetter | 2014-01-06 04:44:14 | == PostgreSQL Weekly News - January 05 2014 == |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-01-06 20:59:53 | Re: dynamic shared memory and locks |
Previous Message | Tom Lane | 2014-01-06 20:57:02 | Re: dynamic shared memory and locks |