Bogdan Calmac wrote:
The attached test is an attempt to simulate a typical data processing
application, it consists of:
- an insert thread that inserts records in batch
- a select thread that 'processes' the records inserted by the other
thread: 'select * from table where id ?'
The test
Is there a way to get a list of indexes on a table including the index
name. I tried using show indexes, but it doesn't give the index name,
just the columns that are indexed. The use case is that i have an
existing db and want to drop an index, but i don't know the name of the
index.
Mike Matrigali wrote:
Ah this makes sense. I didn't take into account internal
transactions. Index split deadlock huh? I would have never thought
of that. Does this happen often?
I almost never see it, but of course every app is different. The
problem is that your test case, I think
because tx6154 doesn't
release its locks. 6154 isn't waiting on anything. Its almost as if
the locks aren't getting released. I think i'm going to try to work on
a simpler example to reproduce this.
-Randy
Kristian Waagan wrote:
Randy Letness skrev:
A little more info:
I have a test program
Oystein Grovlen - Sun Norway wrote:
Randy Letness wrote:
I'm trying to debug a deadlock. There are two transactions: one
updates rows from table foo, and one selects the same rows from table
foo for reading. Is it possible to get in a deadlock in this
situation? I'm using the default
the same
code, different JDBC driver.
-Randy
Oystein Grovlen - Sun Norway wrote:
Randy Letness wrote:
I'm trying to debug a deadlock. There are two transactions: one
updates rows from table foo, and one selects the same rows from
table foo for reading. Is it possible to get in a deadlock
I'm trying to debug a deadlock. There are two transactions: one updates
rows from table foo, and one selects the same rows from table foo for
reading. Is it possible to get in a deadlock in this situation? I'm
using the default READ_COMMITTED transaction level. The transactions
look like:
Mike Matrigali wrote:
Out of curiousity what behavior does Hibernate expect when 2 nulls are
inserted into a unique nullable column?
When you specify a unique constraint in hibernate, I'm pretty sure its
only used by the schema export tools to generate a unique constraint
when generating
