Skip site navigation (1) Skip section navigation (2)

Re: do we EXEC_BACKEND on Mac OS X?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: do we EXEC_BACKEND on Mac OS X?
Date: 2012-10-03 16:41:37
Message-ID: 10986.1349282497@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
I wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Noticed while perusing
>> http://lwn.net/Articles/518306/

> I'm afraid Brian was just looking for an excuse to dump on Apple.  We
> have a lot of years of Postgres experience showing that fork() works
> fine on OS X.

BTW, I think the commenter at the bottom of the thread puts his finger
on the core of the real problem:

> I'd wager most libraries are not fork safe, including such libraries
> as SQLite as mentioned in the SQLite FAQ. Libraries that talk to the
> outside world contain much state that is not safe to share.

To bring that closer to home, suppose you have a program with an open
database connection in libpq, and you fork(), and then parent and child
both try to use the connection.  How well would that work?  Is it the
fault of fork()?

I think Apple is just pointing out that their framework libraries have
similar issues.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2012-10-03 17:08:17
Subject: Re: do we EXEC_BACKEND on Mac OS X?
Previous:From: Tom LaneDate: 2012-10-03 16:26:42
Subject: Re: do we EXEC_BACKEND on Mac OS X?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group