Hi,
I have a stored procedure that is causing deadlocks when called multiple
times synchronously. The odd issue is that the deadlock seems to be
happening on different threads waiting for locks on transactions. What
exactly is this transaction lock?
ERROR: deadlock detected
DETAIL: Process 1
I see from a previous email on the list that someone was able to get
decent debug out of the locks, i.e.
Aug 10 14:19:36 thunder postgres[18735]: [2-1] ERROR: deadlock detected
Aug 10 14:19:36 thunder postgres[18735]: [2-2] DETAIL: Proc 18735 waits
for AccessExclusiveLock on relation 18028 of
Hi,
I've hit a little problem and was wondering if anyone might be able to
give some help.
Set-up:
- JBoss appserver using entity beans to access database
- Using sequence pattern to update primary keys for several tables.
Basically it is a method of getting primary keys without hitting the
d
Not sure about 2.5 million records but try running "VACUUM ANALYSE"
before the delete and during (every now and then).
Had the same problem with 100,000 records and it did the trick nicely.
Hi,
hi have a table with 2.5 million records which i try do delete. i have
several constraints on it too.
Mike Mascari wrote:
Tim McAuley wrote:
Hi,
I have a table which I have populated with over 5000 entries. There is a
combined index placed on two of the columns (both bigint). I am trying
a simple select (i.e. select id where col1 = 1 and col2 = 1) covering
these two columns and it keeps
Hi,
I have a table which I have populated with over 5000 entries. There is a
combined index placed on two of the columns (both bigint). I am trying
a simple select (i.e. select id where col1 = 1 and col2 = 1) covering
these two columns and it keeps using a seq scan. Is this correct? I
would