Re: postgresql locks the whole table!

> If you cannot make your transactons shorter (and
> please don't tell me
> that you have user interaction going on while
> holding any open
> transactions), then you might be able to increase
> your concurrency by
> deferring the foreign key check until commit.

oh! my! gawd!!!
THANK YOU! The deferred foreign key checks are exactly
what I needed. They are quite useful for other reasons
too. I think that should be the default for foreign
keys. Interestingly, the severe concurrency
degradation caused by immediate foreign key checks is
not explained in any of the documentation I looked at.

btw, there is no user interaction during the
transaction, just a lot of CPU- and IO-intensive
processing.

thanks,

Eugene

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree