Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 3E0431A76E95 for ; Thu, 9 Aug 2012 23:07:15 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Szed4-0004h3-M6 for pgsql-admin@postgresql.org; Fri, 10 Aug 2012 02:07:14 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q7A26vHC010483; Thu, 9 Aug 2012 22:06:57 -0400 (EDT) From: Tom Lane To: Greg Williamson cc: "pgsql-admin@postgresql.org" Subject: Re: Question about ALTER TABLE DROP CONSTRAINT on 9.1 -- psql crashes In-reply-to: <1344562260.90632.YahooMailNeo@web125901.mail.ne1.yahoo.com> References: <1344557082.43876.YahooMailNeo@web125906.mail.ne1.yahoo.com> <8579.1344557984@sss.pgh.pa.us> <1344558910.70207.YahooMailNeo@web125906.mail.ne1.yahoo.com> <1344562260.90632.YahooMailNeo@web125901.mail.ne1.yahoo.com> Comments: In-reply-to Greg Williamson message dated "Thu, 09 Aug 2012 18:31:00 -0700" Date: Thu, 09 Aug 2012 22:06:57 -0400 Message-ID: <10482.1344564417@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201208/71 X-Sequence-Number: 39892 Greg Williamson writes: > Every minute on the minute there is a cronjob that kills IDLE IN CONNECTION procs older than 3 seconds ... possibly that process killed the process I was running, but to me the user it seemed as if the COMMIT came before the disconnect. That sure sounds like the source of your problem. It might be sane if it killed only processes that *had been idle* for at least three seconds, but I'm not sure there is any easy way to determine that ... regards, tom lane