Scott Marlowe <scott.marlowe@xxxxxxxxx> writes: > On Mon, Mar 23, 2009 at 2:25 PM, Brian Cox <brian.cox@xxxxxx> wrote: >> This generates and executes a single SQL insert. Since, as you point out, >> postgres seems to think that this transaction isn't doing anything, >> it's hard to figure out what the read is doing. > Might you have a firewall that's killing the connections? What does > netstat -an on the client side say about these connections? netstat will probably say the connection is open on both sides --- otherwise the sockets would have closed. It looks like both sides still think the connection is open. A firewall timeout is still a possibility, but you'd have had to have a fairly long idle time for that to happen. Are any of the threads issuing commands that might have run for very long intervals (tens of minutes)? regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
