| From: | J Sisson <sisson(dot)j(at)gmail(dot)com> |
|---|---|
| To: | wyx6fox(at)sina(dot)com |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: the jokes for pg concurrency write performance |
| Date: | 2010-02-03 08:31:30 |
| Message-ID: | 4297a9021002030031k773f25eu8b41c189fac488ec@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2010/2/1 <wyx6fox(at)sina(dot)com>:
> * 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 .
>
> * joke 2: concurrency update on same row would lead to that other
> transaction must wait the earlier transaction complete , this would kill the
> concurrency performance in some long time transaction situation . a stupid
> design to ,
I hear that MySQL can work wonders in performance by bypassing the
checks you're concerned about...don't count on the data being
consistent, but by golly it'll get to the client FAAAAAAAST...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-02-03 10:23:58 | Re: queries with subquery constraints on partitioned tables not optimized? |
| Previous Message | Greg Smith | 2010-02-03 07:48:19 | Re: System overload / context switching / oom, 8.3 |