Alvaro,
Is there a PostgreSQL bug number that I could refer to for this problem?
Thank you.
On Tue, Jul 9, 2013 at 4:53 PM, Alvaro Herrera wrote:
> Jamey Poirier escribió:
> >
> > Thank you Alvaro. Yes, this explains it.
> > It doesn't help to fix it but at least I know now that it's a known
Doing that just moves the problem from the time of the UPDATE to the time
of the COMMIT.
It is still possible to get a deadlock and I'm not sure how making it
deferrable helps in this case.
You can still end up with a deadlock like this:
CON1: BEGIN;
CON1: SELECT * FROM A WHERE id = 1 FOR UPDATE;
