Received: from news.tht.net (news.hub.org [216.126.91.242]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2H1Aox90566 for ; Fri, 16 Mar 2001 20:10:50 -0500 (EST) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.1/8.11.1) id f2H1Acr46933 for pgsql-hackers@postgresql.org; Fri, 16 Mar 2001 20:10:38 -0500 (EST) (envelope-from news) From: "Kevin T. Manley" X-Newsgroups: comp.databases.postgresql.hackers Subject: transaction timeout Date: Fri, 16 Mar 2001 17:10:14 -0800 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 13 Message-ID: <98udia$1dqg$1@news.tht.net> X-Complaints-To: scrappy@hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 To: pgsql-hackers@postgresql.org X-Archive-Number: 200103/730 X-Sequence-Number: 6063 Is there a timeout setting I can use to abort transactions that aren't deadlocked, but which have been blocked waiting for locks greater than some amount of time? I didn't see anything in the docs on this and observed with 2 instances of psql that a transaction waiting on a lock seems to wait forever. If pgsql doesn't have such a setting, has there been any discussion about adding it? Regards, Kevin Manley