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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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:39:57
Message-ID: 25457.1281497997@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> You probably should close any open file descriptors too, just to be
> safe. (Or do we set FD_CLOEXEC on them?)

We don't. It'd take an extra syscall per open(), which seems like rather
a lot of overhead to deal with a case we aren't even trying to support.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Samantha Atkins 2010-08-11 05:31:24 Re: Is there a way to bypass sql?
Previous Message Alvaro Herrera 2010-08-11 03:35:59 Re: fork() and dynamically loaded c functions....