mber 18, 2009 14:41:09
Subject: Re: [GENERAL] Postgresql Database Lock Problem
At first I would like to thank you all for your quick response.
Now my question is why two processes ID 19181 and 19196 are trying to access
the same transaction 18386574 at the same time.
Here I have got Proces
7:53
Subject: Re: [GENERAL] Postgresql Database Lock Problem
[ cc's trimmed a bit ]
shohorab hossain writes:
> LOG: process 19181 still waiting for ShareLock on transaction 18025221
> after 1002.251 ms
> STATEMENT: SELECT CurrentNext, CurrentNextSys, IncrementNo, Prefix, Suffix
lient_id) REFERENCES
ad_client(ad_client_id) DEFERRABLE INITIALLY DEFERRED
"sequenceorg" FOREIGN KEY (ad_org_id) REFERENCES ad_org(ad_org_id)
DEFERRABLE INITIALLY DEFERRED
With Thanks & Regards:
---------
Shohorab Hossain
- Original Message
From:
Next time this is happening join the pg_lock table to the
pg_stat_activity table to see which query is holding the lock for a
bazillion milliseconds, while it's happening. That query / statement
may give you some clue what's wrong.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql
[ cc's trimmed a bit ]
shohorab hossain writes:
> LOG: process 19181 still waiting for ShareLock on transaction 18025221
> after 1002.251 ms
> STATEMENT: SELECT CurrentNext, CurrentNextSys, IncrementNo, Prefix, Suffix,
> DecimalPattern, AD_Sequence_ID FROM AD_Sequence WHERE Name = $1 AND
> AD_Cl
Problem: Database Lock
--
Dear
all
I
am working as a database administrator in a company. Our Database
system is Postgresql-8.3.5 and Application server is Jboss used for
our Adempiere ERP system. This is a web based ERP system. All
servers are running on RHE
