Re: fork() and dynamically loaded c functions....

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jay Flattery <jaycode(at)rocketmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: fork() and dynamically loaded c functions....
Date: 2010-08-11 03:35:59
Message-ID: 1281497679-sup-708@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Excerpts from Tom Lane's message of mar ago 10 19:49:18 -0400 2010:

> Offhand the only clean way I can see to launch a child process is to
> fork *and exec something*.

You probably should close any open file descriptors too, just to be
safe. (Or do we set FD_CLOEXEC on them?)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-08-11 03:39:57 Re: fork() and dynamically loaded c functions....
Previous Message Tom Lane 2010-08-11 02:59:19 Re: InitDB: Bad system call