agora inbox for pgsql-interfaces@postgresql.org  
help / color / mirror / Atom feed
Problem when forking
2+ messages / 2 participants
[nested] [flat]

* Problem when forking
@ 2015-03-17 14:21  Rodrigo Barboza <rodrigombufrj@gmail.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Rodrigo Barboza @ 2015-03-17 14:21 UTC (permalink / raw)
  To: pgsql-interfaces

Hello everyone,

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?

Maybe close the file descriptor without closing the connection...

This is not causing any trouble, but my log increases very quickly with
useless information.

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Problem when forking
@ 2015-03-23 20:02  Greg Sabino Mullane <greg@turnstep.com>
  parent: Rodrigo Barboza <rodrigombufrj@gmail.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Greg Sabino Mullane @ 2015-03-23 20:02 UTC (permalink / raw)
  To: pgsql-interfaces


-----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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2015-03-23 20:02 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-03-17 14:21 Problem when forking Rodrigo Barboza <rodrigombufrj@gmail.com>
2015-03-23 20:02 ` Greg Sabino Mullane <greg@turnstep.com>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox