Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #74659 > unrolled thread

Re: Blocked thread

Started byChris Angelico <rosuav@gmail.com>
First post2014-07-18 04:04 +1000
Last post2014-07-18 04:04 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Blocked thread Chris Angelico <rosuav@gmail.com> - 2014-07-18 04:04 +1000

#74659 — Re: Blocked thread

FromChris Angelico <rosuav@gmail.com>
Date2014-07-18 04:04 +1000
SubjectRe: Blocked thread
Message-ID<mailman.11941.1405620258.18130.python-list@python.org>
On Fri, Jul 18, 2014 at 4:00 AM, Larry Martell <larry.martell@gmail.com> 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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web