fork() bad

From: Richi Plana <richip(at)mozcom(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: fork() bad
Date: 1999-03-22 13:30:58
Message-ID: Pine.LNX.4.04.9903222125190.2296-100000@jaguar.mozcom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I'm probably doing something wrong here.

My process establishes a connection with a PostgreSQL backen and then
fork()s (twice, actually). To make things even more complicated (though I
don't know if it affects things), my connection handle is a global
variable in a dynamically-loaded shared object.

I tried PQreset()ing the connections after forking and then I'd try a
begin but I'd get the ff.:

NOTICE: BeginTransactionBlock and not in default state

What does that mean?

So, what's the deal with fork()ing and connections?

L L Richi Plana 8^) ,-,-. ,-,-. ,-,-. ,-,-. ,-
LL LL Systems Administrator / / \ \ / / \ \ / / \ \ / / \ \ / /
LLLLL Mosaic Communications, Inc. \ \ / / \ \ / / \ \ / / \ \ / /
LLLLL mailto:richip(at)mozcom(dot)com `-'-' `-'-' `-'-' `-'-'
------------------------------------------------------------------------
P G P Key available at http://www2.mozcom.com/~richip/richip.asc
Tired of Spam? Join this CAUCE! http://www.cauce.org/

Responses

Browse pgsql-general by date

  From Date Subject
Next Message M Simms 1999-03-22 14:08:51 Re: [GENERAL] fork() bad
Previous Message Richi Plana 1999-03-22 12:30:26 max # concurrent?