Re: transaction safety

From: DaVinci <bombadil(at)wanadoo(dot)es>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: transaction safety
Date: 2001-02-14 10:05:56
Message-ID: 20010214110556.A2081@fangorn.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Feb 13, 2001 at 09:52:21AM -0500, Tom Lane wrote:
> DaVinci <bombadil(at)wanadoo(dot)es> writes:
> > procedencia int2 references procedencia,
> > lnea int2 references lnea,
> > empresa int2 references empresa,
>
> Depending on the data values you are working with, it could be that the
> foreign key references cause interlocks --- ie, one transaction has to
> wait to see if the other commits to know if it has a valid foreign key.

Problem is with referential integrity like you say. But I don't understand
well reason. Interlocks should appear only when values of referenced tables
are changed, added or removed, shouldn't they?. But that is not the case. I
only insert in table "aviso".

Is this normal?

Greets.

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Uro Gruber 2001-02-14 11:32:20 Crash-me of PostgreSQL
Previous Message Matt Friedman 2001-02-14 08:24:52 Re: Re: Bad book review