On Fri, 05 Jun 2009 17:35:19 -0400
Tom Lane wrote:
> Ivan Sergio Borgonovo writes:
> > I don't get it.
> > Why dropping the triggers would cause a deadlock anyway?
>
> > I bet it is due to my naïve view of the problem but I think a
> > trigger is a "function". Unless there is concurrent access
Ivan Sergio Borgonovo writes:
> I don't get it.
> Why dropping the triggers would cause a deadlock anyway?
> I bet it is due to my naïve view of the problem but I think a
> trigger is a "function". Unless there is concurrent access to the
> table where the function is defined... I can't see why
On Fri, 05 Jun 2009 10:46:11 -0400
Tom Lane wrote:
> Ivan Sergio Borgonovo writes:
> > I've encountered this error for the first time
> > psql:./import_stock_scratch.sql:9: ERROR: deadlock detected
> > DETAIL: Process 11095 waits for AccessExclusiveLock on relation
> > 250545 of database 24856
Ivan Sergio Borgonovo writes:
> I've encountered this error for the first time
> psql:./import_stock_scratch.sql:9: ERROR: deadlock detected
> DETAIL: Process 11095 waits for AccessExclusiveLock on relation
> 250545 of database 248569; blocked by process 11099. Process 11099
> waits for AccessSh
I've encountered this error for the first time
psql:./import_stock_scratch.sql:9: ERROR: deadlock detected
DETAIL: Process 11095 waits for AccessExclusiveLock on relation
250545 of database 248569; blocked by process 11099. Process 11099
waits for AccessShareLock on relation 250510 of database 2
