Re: the jokes for pg concurrency write performance

2010/2/1 <wyx6fox(at)sina(dot)com>:
> hi, first, thanks u for make so good opensource db .
>
> recently maybe half an years ago ,i begin to use pg in a big project for
> insurance project, belong as the project go on ,and
>
> i found some performance problem on concurrency write situation , then i do
> a research on concurrency write strategy on postgresql ,
>
> i found a joke ,maybe this joke concurrency strategy is the designer's
> pround idea, but i think it is a joke , next let me describe the problems:

Please try not to insult the people you're asking for help. Maybe a
little less inflamatory language. Something like "It seems that there
are some issues with concurrency" would work wonders. It's amazing
how much better a response you can get wihtout insulting everybody on
the list, eh?

Let's rewrite this assertion:
> * joke 1: insert operation would use a excluse lock on reference row by the
> foreign key . a big big big performance killer , i think this is a stupid
> design .

"problem #1: insert operation would use a excluse lock on reference row by the
foreign key . a big big big performance killer. "

Then post an example of how it affects your performance. Did you go
to the page that was pointed out to you in a previous post on how to
post effectively about pg problems and get a useful answer? If not,
please do so, and re-post your questions etc without all the insults
and hand waving.