From: Scott Marlowe <scott.marlowe@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: wyx6fox@sina.com
Cc: pgsql-performance@postgresql.org
Subject: Re: the jokes for pg concurrency write performance
Date: Tue, 2 Feb 2010 09:27:26 -0700
Message-ID: <dcc563d11002020827u2dfe579cv9217f64b0ceb98b2@mail.gmail.com> (raw)
In-Reply-To: <20100202162046.GA4020@alvh.no-ip.org>
References: <20100202045701.93A404B1C73@mail175-236.sinamail.sina.com.cn>
<dcc563d11002020812t4a3ce023q2049630313a8f531@mail.gmail.com>
<20100202162046.GA4020@alvh.no-ip.org>
On Tue, Feb 2, 2010 at 9:20 AM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Scott Marlowe escribió:
>> 2010/2/1 <wyx6fox@sina.com>:
>
>> 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. "
>
> Yeah, if it had been written this way I could have told him that this
> is not the case since 8.1, but since he didn't, I simply skipped his
> emails.
I wonder if having paid technical support to abuse leads to people
thinking they can treat other people like crap and get the answer they
want anyway... Well, we'll see if the OP can write a non-flame-filled
inquiry on their performance issues or not.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, alvherre@commandprompt.com, wyx6fox@sina.com
Subject: Re: the jokes for pg concurrency write performance
In-Reply-To: <dcc563d11002020827u2dfe579cv9217f64b0ceb98b2@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox