From: Craig Ringer <ringerc@ringerc.id.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Williamson <gwilliamson39@yahoo.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Question about ALTER TABLE DROP CONSTRAINT on 9.1 -- psql crashes
Date: Fri, 10 Aug 2012 10:24:40 +0800
Message-ID: <502470E8.4010807@ringerc.id.au> (raw)
In-Reply-To: <10482.1344564417@sss.pgh.pa.us>
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>
<10482.1344564417@sss.pgh.pa.us>
On 08/10/2012 10:06 AM, Tom Lane wrote:
> Greg Williamson <gwilliamson39@yahoo.com> 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 ...
wouldn't:
select * from pg_stat_activity
where current_query = '<IDLE> in transaction'
AND query_start < current_timestamp - INTERVAL '3 seconds';
do it?
--
Craig Ringer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ringerc@ringerc.id.au, tgl@sss.pgh.pa.us, gwilliamson39@yahoo.com
Subject: Re: Question about ALTER TABLE DROP CONSTRAINT on 9.1 -- psql crashes
In-Reply-To: <502470E8.4010807@ringerc.id.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox