Re: idle in transaction query makes server unresponsive

From: Chris Travers <chris(dot)travers(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: "Scot Kreienkamp *EXTERN*" <SKreien(at)la-z-boy(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: idle in transaction query makes server unresponsive
Date: 2012-09-27 07:48:04
Message-ID: CAKt_Zft42oRApV=WbeVh8+0REde8Aah9VNfnu2apPg6HsLEz+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

If it is truly idle in a transaction, maybe it has locks that are holding
up other transactions?

Locks are usually held until commit time, except advisory locks iirc but
those have to be explicitly checked, so if you don't know if you are using
them you probably aren't.

Long-running transactions are generally a problem particularly when you
have idle blocks of space between them. Try shortening your transactions
and see if that helps.

Best Wishes,
Chris Travers

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2012-09-27 10:21:54 Re: idle in transaction query makes server unresponsive
Previous Message Albe Laurenz 2012-09-27 07:42:59 Re: idle in transaction query makes server unresponsive