fork/exec problem: DynaHashCxt - Mailing list pgsql-hackers

From Claudio Natoli
Subject fork/exec problem: DynaHashCxt
Date
Msg-id A02DEC4D1073D611BAE8525405FCCE2B028063@harris.memetrics.local
Whole thread Raw
Responses Re: fork/exec problem: DynaHashCxt
List pgsql-hackers
Hi all,

I'm working on getting BackendFork converted to a fork/exec model, and have
hit the following wall.

All the ShmemInitHash structures are allocated using DynaHashCxt. Clearly,
this context is going to have to be shared across backends in the fork/exec
case, but I can't see a non-trivial way of doing so.

Any ideas? (or have I mis-diagnosed the problem completely)

Cheers,
Claudio

---
Certain disclaimers and policies apply to all email sent from Memetrics.
For the full text of these disclaimers and policies see
<a
href="http://www.memetrics.com/emailpolicy.html">http://www.memetrics.com/em
ailpolicy.html</a>

pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: request for feedback - read-only GUC variables,
Next
From: david@fetter.org (David Fetter)
Date:
Subject: Inside the Regex Engine