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

From Bruce Momjian
Subject Re: fork/exec patch
Date
Msg-id 200312142221.hBEMLmT20146@candle.pha.pa.us
Whole thread Raw
In response to Re: fork/exec patch  (Dennis Bjorklund <db@zigo.dhs.org>)
Responses Re: fork/exec patch  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-patches
Dennis Bjorklund wrote:
> 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.

Doesn't that require the postmaster to stay around to feed that
information into the pipe or can the postmaster just shove the data and
continue on, and how do the old pipes get cleaned up?  Seems messy.
Also has to work on Unix too for testing.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: fork/exec patch
Next
From: Dennis Bjorklund
Date:
Subject: Re: fork/exec patch