Re: fork/exec patch - Mailing list pgsql-patches

From Dennis Bjorklund
Subject Re: fork/exec patch
Date
Msg-id Pine.LNX.4.44.0312142306560.10157-100000@zigo.dhs.org
Whole thread Raw
In response to Re: fork/exec patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: fork/exec patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
On Sun, 14 Dec 2003, Bruce Momjian wrote:

> change to the code.  We already have a GUC write of non-default values
> for exec and no one had issues with that.  Of course, this one is
> per-backend.
>
> Yea, we could use shared memory for this too, but I don't see a problem
> with using the file system.

Why not use an anonymous pipe to send data from the parent to the child
process? That is a common way to handle this problem in win32 (and in unix
by the way). The parent sets up the pipe and the child process inherits
the handle, and after that the child and parent can excange information in
private.

--
/Dennis


pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: fork/exec patch
Next
From: Bruce Momjian
Date:
Subject: Re: fork/exec patch