Re: function transaction scope question

From: John DeSoi <desoi(at)pgedit(dot)com>
To: "Wright, George" <George(dot)Wright(at)infimatic(dot)com>
Cc: "PostgreSQL List - Novice" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: function transaction scope question
Date: 2009-01-15 15:06:04
Message-ID: C200C004-B7D7-4F51-8CD2-36AFA7BAA5C6@pgedit.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice


On Jan 15, 2009, at 8:43 AM, Wright, George wrote:

> Then if there is a large amount of code all wrapped by a single
> transaction and it hangs somewhere in the code, what technique can be
> used to abort the transaction? (It's not really a deadlock)

I believe there is a statement timeout setting where an automatic
abort could be executed. If you want to abort a running query manually
see pg_cancel_backend:

http://www.postgresql.org/docs/8.3/interactive/functions-admin.html

John DeSoi, Ph.D.

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Jasen Betts 2009-01-17 11:32:11 Re: debugging plpgsql functions
Previous Message Tom Lane 2009-01-15 15:03:30 Re: order by differences: locale problem?