Re: WHY transaction waits for another transaction?

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Vilinski Vladimir <vilinski(at)web(dot)de>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: WHY transaction waits for another transaction?
Date: 2005-06-19 16:22:09
Message-ID: 20050619162209.GA19463@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Sun, Jun 19, 2005 at 09:58:11AM -0600, Michael Fuhr wrote:
>
> If possible, it would be best to commit transactions that insert
> or update foreign keys as soon as possible.

I probably shouldn't have said "best" here, implying that this
solution is better than all other possibilities. As Tom Lane pointed
out, you could also make the constraints deferrable. If you don't
need to know about foreign key violations immediately, then deferring
the checks might be a better way to go.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2005-06-19 18:46:24 Re: Putting an INDEX on a boolean field?
Previous Message Michael Fuhr 2005-06-19 15:58:11 Re: WHY transaction waits for another transaction?