2010/2/1 <wyx6...@sina.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... -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
