Let us know in about a month what your database references look like :-) without
table locks, which cause the same problem that you're trying to fix, I don't
think that it's possible to maintain referential integrity with multiple
processes going .... in application code.
I've been proved wrong on many things, I hope for your sake that this is one of
them :-)
Chris Hutchinson wrote:
> Thanks to everyone for their suggestions on dealing with inserts blocked by
> index locking.
>
> My eventual solution was to remove the REFERENCES constraints on the
> affected tables and move referential integrity into the application - not
> ideal, but faster to implement than the alternatives.
>
> Suggested solutions were:
> * Load file into temporary table, and insert into primary table from
> temporary (Dennis Gearon, David Olberson)
> * Convert data to insert statements and (I think) run each in a separate
> transaction (Jeff Eckerman)
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
