Re: postgresql locks the whole table!

Dr NoName wrote:

>> 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

The way it is is the way it is defined by the standard.


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #