Re: INSERT/SELECT and excessive foreign key checks

From: Lodewijk Vöge <lvoege(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: INSERT/SELECT and excessive foreign key checks
Date: 2007-08-21 14:35:01
Message-ID: FF90C38D-0939-4C55-B73C-67516051D5E6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19-aug-2007, at 12:38, Tom Lane wrote:

> An additional problem with your proposal is that it fails to consider
> other changes that might be happening concurrently -- eg, what if some
> other backend deletes a source row after you copy it, and commits
> before
> you do?

then the patch indeed failed, but when I change it to check those
carried over FKs also once, it catches it correctly.

are there other such issues? or is this kind of optimization not
going in no matter what?

Lodewijk

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-08-21 14:42:19 Re: tsearch2 patch status report
Previous Message Kevin Grittner 2007-08-21 14:34:17 Re: 8.3 beta testing suggestions welcome