Re: Should libpq set close-on-exec flag on its socket? - Mailing list pgsql-hackers

From dom@happygiraffe.net (Dominic Mitchell)
Subject Re: Should libpq set close-on-exec flag on its socket?
Date
Msg-id 20041022115303.GA62269@ppe.happygiraffe.net
Whole thread Raw
In response to Should libpq set close-on-exec flag on its socket?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Oct 21, 2004 at 02:10:48PM -0400, Tom Lane wrote:
> It was suggested to me off-list that libpq should do
> "fcntl(fd, F_SETFD, FD_CLOEXEC)" on the socket connecting to the server.
> This would prevent any child program from accidentally or maliciously
> interfering with the connection.  It would also prevent people from
> deliberately turning over a connection to a child; I'm not sure that
> that's useful, but I'm not sure it's useless either.
> 
> Comments, opinions?

This is a very good idea.  We've had problems with Perl programs that
call other scripts (over an exec boundary) and end up with unnecessary
DBD::Pg file handles hanging around.  This would be good to prevent
that.

-Dom


pgsql-hackers by date:

Previous
From: "Michael Paesold"
Date:
Subject: Re: code question: storing INTO relation
Next
From: Robert Treat
Date:
Subject: Re: timestamp with time zone a la sql99