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


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

Re: Blocked thread

Started byLarry Martell <larry.martell@gmail.com>
First post2014-07-17 14:00 -0400
Last post2014-07-17 14:00 -0400
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 Larry Martell <larry.martell@gmail.com> - 2014-07-17 14:00 -0400

#74657 — Re: Blocked thread

FromLarry Martell <larry.martell@gmail.com>
Date2014-07-17 14:00 -0400
SubjectRe: Blocked thread
Message-ID<mailman.11938.1405620049.18130.python-list@python.org>
On Thu, Jul 17, 2014 at 1:46 PM, Skip Montanaro <skip@pobox.com> wrote:
>
> On Thu, Jul 17, 2014 at 12:32 PM, Chris Angelico <rosuav@gmail.com> wrote:
>>
>> I don't know Oracle specifically, but if it's anything like
>> PostgreSQL, you'll probably do better with a completely separate
>> connection to the server
>
>
> Agreed. We use Sybase, and our DBA uses their tools extensively to identify
> problematic clients.

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.

[toc] | [standalone]


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


csiph-web