Re: Feature thought: idle in transaction timeout

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature thought: idle in transaction timeout
Date: 2007-04-03 04:12:07
Message-ID: 200704030412.l334C7b09126@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


TODO updated:

* Add idle_in_transaction_timeout GUC so locks are not held for long
periods of time

---------------------------------------------------------------------------

Joshua D. Drake wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >> Bruce Momjian wrote:
> >>> Added to TODO:
> >>> * Add idle_timeout GUC so locks are not held for log periods of time
> >
> >> That should actually be transaction_idle_timeout. It is o.k. for us to
> >> be IDLE... it is not o.k. for us to be IDLE in Transaction
> >
> > Or "idle_in_transaction_timeout"?
>
> Yeah that would work and it is what I originally typed before
> backspacing. I was trying to avoid the _in_ but either way.
>
> > Anyway I agree that using
> > "idle_timeout" for this is unwise. We've been asked often enough for a
> > flat-out idle timeout (ie kill session after X seconds of no client
> > interaction), and while I disagree with the concept, someday we might
>
> Well I agree that we shouldn't kill sessions just because they are idle,
> I can imagine all the lovely... my pgpool sessions keep getting killed!
> comments.
>
> > cave and implement it. We should reserve the name for the behavior
> > that people would expect a parameter named like that to have.
>
> Agreed.
>
> Sincerely,
>
> Joshua D. Drake
>
> >
> > regards, tom lane
> >
>
>
> --
>
> === 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
> http://www.commandprompt.com/
>
> Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
> PostgreSQL Replication: http://www.commandprompt.com/products/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Browne 2007-04-03 04:18:16 Re: Modifying TOAST thresholds
Previous Message Hideyuki Kawashima 2007-04-03 03:49:27 Re: Acclerating INSERT/UPDATE using UPS