Re: Detecting libpq connections improperly shared via fork() - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Detecting libpq connections improperly shared via fork()
Date
Msg-id 506CEC1E.3010101@dunslane.net
Whole thread Raw
In response to Re: Detecting libpq connections improperly shared via fork()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 10/03/2012 09:23 PM, Tom Lane wrote:

> A bigger problem with this is that it only fixes the issue for cases in
> which somebody makes new threads of control with fork().  I believe that
> issues involving multiple threads trying to use the same PGconn are at
> least as widespread.  I'm not terribly excited about removing
> functionality and adding overhead to protect against just one variant of
> the problem.
>
>             

I had the same thought re threads.

cheers

andrew




pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: FDW for PostgreSQL
Next
From: Greg Stark
Date:
Subject: Re: Support for REINDEX CONCURRENTLY