Skip site navigation (1) Skip section navigation (2)

Feature thought: idle in transaction timeout

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Feature thought: idle in transaction timeout
Date: 2007-03-29 20:25:12
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers

I ran into an interesting problem with a customer today. They are 
running Jabber XCP (not the one we use). Unfortunately, the product has 
a bug that causes it to leave connections persistent in a transaction 
state. This is what it does:


Basically it is verifying that the connection is live. However, it never 
calls commit. So what happens? We can't vacuum ;).

Anyway, my thought is, we know when a transaction is idle, why not have 
an idle timeout where we will explicitly close the connection or 
rollback or something? User configurable of course.


Joshua D. Drake


       === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project:
PostgreSQL Replication:


pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-03-29 20:28:36
Subject: Re: [PATCHES] Full page writes improvement, code update
Previous:From: Simon RiggsDate: 2007-03-29 20:04:11
Subject: Re: CREATE INDEX and HOT - revised design

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group