| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> |
| Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>, "'PostgreSQL Win32 port list'" <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] fork/exec problem: DynaHashCxt |
| Date: | 2003-12-03 04:12:04 |
| Message-ID: | 26797.1070424724@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 |
Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> writes:
> All the ShmemInitHash structures are allocated using DynaHashCxt.
I'm not sure if you're confusing backend-local hashes with shared
hashes, or hash control headers with the actual shared data. But
the above is a false statement. DynaHashCxt is not shared.
Shared hashes are a bit tricky because there is a backend-local
structure that has a pointer into the shared memory --- is that
what's confusing you?
Keep in mind that this code did work in a fork/exec context not
so many moons ago. If you think you see a showstopper, it's a
relatively recent change and can be undone.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2003-12-03 04:12:24 | 7.3.5 bundled ... |
| Previous Message | Tom Lane | 2003-12-03 04:05:42 | Re: Inside the Regex Engine |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Natoli | 2003-12-03 04:48:42 | Re: [HACKERS] fork/exec problem: DynaHashCxt |
| Previous Message | Claudio Natoli | 2003-12-03 01:36:59 | fork/exec problem: DynaHashCxt |