Re: Processes and caches in postgresql - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Processes and caches in postgresql
Date
Msg-id CAHyXU0wrkuRaFyB3ocrBsq3o-=7pxcOW_TB6pFC9_58_-yi1jQ@mail.gmail.com
Whole thread Raw
In response to Re: Processes and caches in postgresql  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Processes and caches in postgresql  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Mon, May 2, 2016 at 7:36 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Apr 27, 2016 at 7:07 AM, Anastasia Lubennikova
> <a.lubennikova@postgrespro.ru> wrote:
>> Hi, hackers.
>> There's a couple of questions about processes.
>>
>> I found EXEC_BACKEND flag, while reading the code.
>> As I understood, it exists because we have to emulate fork() on WIN32.
>> And also it allows to debug the same behavior on Linux.
>> Is it right? Are there any other use cases?
>
> Right.  Or, more precisely, we can't really emulate fork(), so we have
> to make due with what's available on Windows, which is basically
> exec().

There is library out there, unfortunately GPL licensed, that attempts
to fully implement posix including fork(): http://midipix.org/.  One
of these days I'd like to have a go at porting postgres to it.  Maybe
one day we can get rid of all that exec backend stuff :-).

merlin



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgindent fixups
Next
From: Tom Lane
Date:
Subject: Re: pgindent fixups