From: "Greg Sabino Mullane" <greg@turnstep.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: Problem when forking
In-Reply-To: 
 <CANs8QJYUu4QYpGV963_xdBjX+gUWAMFct_-At80KtvzwHdqzqg@mail.gmail.com>
Content-type: text/plain; charset=UTF-8
Date: Mon, 23 Mar 2015 20:02:47 -0000
Message-ID: <2ec30f86c6dae08c20fdf53aa3ce20f0@biglumber.com>
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> I am seeing too many messages like "unexpected EOF on client connection".
> I've made a reasearch and I know the reason: I have processes that fork and
> don't close the connection causing those warnings.
>
> My questions is: is there a way to avoid that behavior beside of closing
> the connection before forking?

You can fork, you just have to make sure one side keeps talking to Postgres 
like normal, and the other should pretend Postgres is not there. It 
should also not do anything that would affect the first connection.

In general, it is a really good rule to fork *then* connect.

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201503231601
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlUQcUQACgkQvJuQZxSWSsh6eACdHvemvFLrV3VIZtECAOZB6gjX
BjoAoKGOoKc2yKDAfi5M2siDMMMjazaC
=kV9C
-----END PGP SIGNATURE-----


-- 
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces