Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 377421DEF5C5 for ; Thu, 9 Aug 2012 21:37:52 -0300 (ADT) Received: from nm10-vm1.bullet.mail.ne1.yahoo.com ([98.138.91.75]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SzdEc-0003Uz-9u for pgsql-admin@postgresql.org; Fri, 10 Aug 2012 00:37:51 +0000 Received: from [98.138.90.52] by nm10.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 00:35:10 -0000 Received: from [98.138.87.3] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 00:35:10 -0000 Received: from [127.0.0.1] by omp1003.mail.ne1.yahoo.com with NNFMP; 10 Aug 2012 00:35:10 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 633513.67138.bm@omp1003.mail.ne1.yahoo.com Received: (qmail 75028 invoked by uid 60001); 10 Aug 2012 00:35:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1344558910; bh=c9hEQ6WB/t7ckbz6ozzKVoxKQLgViC7OqWeTtHLMEjs=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PMqAJtNlzb4/x0vnaZ/bhOj1rkhyino9exxCfnOFgcLlTjgBpl+8JxYropdtNQB4bJY9vBI0QnJ6k2PcPWHKIu4gkXq2j0t3SOpWFGjIxQZEt0pFbYpfHIcYJMW5ReM+HssschcCCr6wBfvmK+oyA+KaEEBrlJpV+gjpSR+it60= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=s1ui/139T40zLPoJipbZd1ei38X193q5ah8fh+FT/yrQiXjZtwsUeQYjm1eD+kDYLbKTJ7w32cAagVuGcU6lgdcKQViwyBOIO4aJzoCjM0i+3nfKKEK+gtcMJskBVSwJ6as+ItyD8FV4txeqpVjMrYJ4Yl5xYZm+P3PnbVJn9s0=; X-YMail-OSG: b92.iaoVM1lT4vX6j6y.pxZ.ps60ZRO_g_PdqjXUfYlnM0Z 6oZIeheVoGTUMItRRXpBT3qdtyZy4ThLS2pMwDHCZj7PDd6QacPsHwzAC8M4 rzNwNZ3RSczUafjBzHJCQwzpm5xT6gx57ZrlcCEZjtzFHZJHAVe7dQEludN_ GfvrR7AeYptO9LDie9RHziuqUdLJBcDE7i8kPszjkVAEdzBdDMlQFZvUL021 XPzwdqHrJ3dbU5Sz4RHLdRPo6BVRrym80tFFjWJKmPjjr3AhdEeSAAaxxET7 W6XAAygx4WoR_aWP7vXxzvpy1c6wSnwYMTsKLaOHWoKemyGiE3DFqTtCqdD1 GwYtUmCN5DMecSuYJ1LfDqHm5mc0hn7B2z8vwRCYLeic1QPH8OFEwWi.SlTZ XEfL_eo4aUurlGXNY2CJqwLBm98iS.xLyyc1GOQ8cZkj5K4GDPRSQa6zP7ud ejLQvBlz9DAoMN0Jgrw-- Received: from [199.9.251.45] by web125906.mail.ne1.yahoo.com via HTTP; Thu, 09 Aug 2012 17:35:10 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: <1344557082.43876.YahooMailNeo@web125906.mail.ne1.yahoo.com> <8579.1344557984@sss.pgh.pa.us> Message-ID: <1344558910.70207.YahooMailNeo@web125906.mail.ne1.yahoo.com> Date: Thu, 9 Aug 2012 17:35:10 -0700 (PDT) From: Greg Williamson Reply-To: Greg Williamson Subject: Re: Question about ALTER TABLE DROP CONSTRAINT on 9.1 -- psql crashes To: Tom Lane Cc: "pgsql-admin@postgresql.org" In-Reply-To: <8579.1344557984@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="452707994-1904311350-1344558910=:70207" X-Pg-Spam-Score: 0.5 (/) X-Archive-Number: 201208/69 X-Sequence-Number: 39890 --452707994-1904311350-1344558910=:70207 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Tom -- >________________________________ ><...>>=A0 >> WTF?=A0 That should certainly not happen.=A0 Have you perhaps got a scri= pt >> that runs around sending SIGTERM to backends that it thinks are blocking >> something?=A0 Does anything show up in the postmaster log when this >> happens? > >No, we have processes that kill IDLE IN TRANSACTIONs ruthlessly, but nothi= ng that kills any other processes. There is an outside chance that this ran= at just the same time that a cronjob ran the REINDEX command for the table= (unlikely but I am going to shut off the cronjob and try this again). > > >It does not log an ERROR to the log file; I can wade intio the log and see= what else it says but it will take a little while (about 800 megs per hour= ) to answer that. > > >Thanks, and I'll report back soon. > > >Greg >- > > > > >= --452707994-1904311350-1344558910=:70207 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Tom --

<...>=
> 
> WTF?  That should certainly not ha= ppen.  Have you perhaps got a script
> that runs around sending = SIGTERM to backends that it thinks are blocking
> something?  Do= es anything show up in the postmaster log when this
> happens?
No, we have processes that kill IDLE IN TRANSACTIONs ruthlessly, but nothi= ng that kills any other processes. There is an outside chance that this ran= at just the same time that a cronjob ran the REINDEX command for the table (unlike= ly but I am going to shut off the cronjob and try this again).

It does not log an ERROR to the log file; I can= wade intio the log and see what else it says but it will take a little whi= le (about 800 megs per hour) to answer that.


Thanks, and I'll re= port back soon.

=
Greg
-
=


= --452707994-1904311350-1344558910=:70207--