Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.014 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'scripts': 0.03; 'causing': 0.04; 'detect': 0.07; 'cc:addr:python-list': 0.11; 'blocking': 0.16; 'competent': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; "he'll": 0.16; 'it."': 0.16; 'wrote:': 0.18; 'cc:addr:python.org': 0.22; 'him.': 0.24; 'cc:2**0': 0.24; 'tables': 0.26; 'gets': 0.27; 'header:In-Reply- To:1': 0.27; 'am,': 0.29; 'message-id:@mail.gmail.com': 0.30; 'info.': 0.31; 'larry': 0.31; 'operations.': 0.31; 'this.': 0.32; 'figure': 0.32; 'fri,': 0.33; 'problem': 0.35; 'knows': 0.35; "who's": 0.35; 'but': 0.35; 'received:google.com': 0.35; "he's": 0.36; 'done': 0.36; 'next': 0.36; 'server': 0.38; 'that,': 0.38; 'how': 0.40; 'monitoring': 0.61; 'situation': 0.65; 'jul': 0.74; '4:00': 0.84; 'dba': 0.84; 'to:none': 0.92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=TS4nCiC2QXMSLlZBdrvLP030q6ceGZmr7JbBlET4vUY=; b=hwlsi+x93vrBHW4vxc4FQhKdD8HtJLnJjt3T3FJFOlpLpendOITHKS7XYFGw0W1MgO 5ggeaZxxhXw4vklsXwOZzFxvztNAxKJq9ycR1Dk2NzazjZB1cN+sVY7b9y10CUFjAgiD Wm2aN0mu3XeM0cwEhQ3NoQLa1FupLaUGvzbwfJmNKtSpFE7GCQLiZptCZm8qhMbkmqzb OK/ETe11bY585uU2iPtlootL+ah6B/XN7Km7tnKOLcnpY9OOLJGbvbPkN1fdLFBQHQHa mcuHSs/65C1GAgQ3reuuCLQJ3eFz7g83L3pwbu5GH05sfzlJXhda+SKUjutV3+M2aI0V 8CzQ== MIME-Version: 1.0 X-Received: by 10.52.248.232 with SMTP id yp8mr12435457vdc.83.1405620249635; Thu, 17 Jul 2014 11:04:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 18 Jul 2014 04:04:09 +1000 Subject: Re: Blocked thread From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 18 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1405620258 news.xs4all.nl 2895 [2001:888:2000:d::a6]:59667 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:74659 On Fri, Jul 18, 2014 at 4:00 AM, Larry Martell wrote: > I did ask my DBA - he said "Blocking is a normal part of database > operations. It's only a problem when it's a deadlock, in which case > the server will detect that, kill one of the processes and log it." > > My situation is not a deadlock - there's just multiple scripts hitting > the same tables at the same time. When one gets done the next one > proceeds. I just want to find out what are the other processes causing > this. Then you definitely want server-side info. The DB server's the one who knows who's waiting on whom. See if your DBA can help you with the specifics; this will be bread-and-butter monitoring work for him. Automating it might require some tweaking, but if he's at all competent at his job, he'll know how to figure out (if manually) what's blocking an important query. ChrisA