From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: EXEC_BACKEND |
Date: | 2008-09-23 20:50:47 |
Message-ID: | 1222203047.4445.468.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2008-09-23 at 16:35 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> >
> > > > I can't find anything coherent in docs/readme/comments to explain why it
> > > > exists and what its implications are.
> > >
> > > It exists because Windows doesn't have fork(), only the equivalent of
> > > fork-and-exec. Which means that no state variables will be inherited
> > > from the postmaster by its child processes, and any state that needs to
> > > be carried across has to be handled explicitly. You can define
> > > EXEC_BACKEND in a non-Windows build, for the purpose of testing code
> > > to see if it works in that environment.
> >
> > OK, if its that simple then I see why its not documented. Thanks. I
> > thought there might be more to it than that.
>
> I added a little documentation at the top of
> postmaster.c::backend_forkexec().
Thanks.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-09-23 21:10:33 | Re: parallel pg_restore |
Previous Message | Andrew Dunstan | 2008-09-23 20:50:43 | Re: parallel pg_restore |