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

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

              http://www.postgresql.org/docs/faq

Reply via email to