| From: | Rodrigo Barboza <rodrigombufrj(at)gmail(dot)com> |
|---|---|
| To: | pgsql-interfaces <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Problem when forking |
| Date: | 2015-03-17 14:21:02 |
| Message-ID: | CANs8QJYUu4QYpGV963_xdBjX+gUWAMFct_-At80KtvzwHdqzqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2015-03-23 20:02:47 | Re: Problem when forking |
| Previous Message | Bill Clay | 2015-03-03 19:47:05 | Re: libpq connect keepalive* parms: no effect!? |