| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ranjeet Singh03 <Ranjeet_Singh03(at)infosys(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: postgres client connection issue |
| Date: | 2017-02-04 15:56:56 |
| Message-ID: | 9956.1486223816@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I wrote:
> it sure looks like this is basically a network problem: something in
> between is killing the connection.
BTW, in case it's not obvious, you should now be thinking in terms of
"localize the network problem", and PG might be able to help you with
that. If the client connections are coming from multiple places, pay
attention to which one(s) are seeing problems. The default logging
options you seem to be using aren't going to be much help, but you could
turn on log_connections and/or log_disconnections, and adjust
log_line_prefix to help you identify just which connections are losing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | joel.traf | 2017-02-05 21:51:58 | plpython bug |
| Previous Message | Tom Lane | 2017-02-04 15:32:01 | Re: postgres client connection issue |