| From: | james <james(at)mansionfamily(dot)plus(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 21:04:09 |
| Message-ID: | 52CB1A49.5060700@mansionfamily.plus.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-announce pgsql-hackers |
On 06/01/2014 04:20, Amit Kapila wrote:
> Duplicate handle should work, but we need to communicate the handle
> to other process using IPC.
Only if the other process needs to use it. The IPC is not to transfer
the handle to
the other process, just to tell it which slot in its handle table
contains the handle.
If you just want to ensure that its use-count never goes to zero, the
receiver does
not need to know what the handle is.
However ...
The point remains that you need to duplicate it into every process that
might
want to use it subsequently, so it makes sense to DuplicateHandle into the
parent, and then to advertise that handle value publicly so that other
child
processes can DuplicateHandle it back into their own process.
The handle value can change so you also need to refer to the handle in the
parent and map it in each child to the local equivalent.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-01-06 21:16:38 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| Previous Message | james | 2014-01-06 20:59:13 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-01-06 21:16:38 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
| Previous Message | Robert Haas | 2014-01-06 20:59:53 | Re: dynamic shared memory and locks |