Re: Locking when concurrent updated of foreign references

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jesper Krogh <jesper(at)krogh(dot)cc>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Locking when concurrent updated of foreign references
Date: 2011-04-11 21:30:53
Message-ID: 1302557439-sup-5596@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Jesper Krogh's message of lun abr 11 17:07:33 -0300 2011:

> But when the locking is done "row-level" then it is correct
> to do it that way. It would allthough be nice with a weaker
> locklevel for that kind of updates (I have no clue if that is
> a hard problem).

http://www.commandprompt.com/blogs/alvaro_herrera/2010/11/fixing_foreign_key_deadlocks/

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-04-11 22:06:19 Re: POSIX shared memory redux
Previous Message Зотов Роман 2011-04-11 20:39:32 Re: Prefered Types