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
Tim McAuley <[EMAIL PROTECTED]> writes:
> 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 wait
On Wednesday 24 September 2003 17:40, Tim McAuley wrote:
> 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.
>
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
