> the unique constraints actualy kill concurrency write transaction when
> concurrency insert violate the unique constraints , they block each other ,
> i test this in oracle10g, has the same behavour. I think this may be
> reasonable because the uqniue check must be the seriazable check .
> for resolve this problem , i do the unique check in application as possible
> , but in big concurrency env , this is not good way .
You may find that your way isn't actually very reliable, and that
making it reliable will be very, very much harder (and likely no
faster) than letting PostgreSQL do it.
In response to
pgsql-performance by date
|Next:||From: Amitabh Kant||Date: 2010-02-03 15:10:57|
|Subject: Optimizing Postgresql server and FreeBSD for heavy read and writes|
|Previous:||From: Andres Freund||Date: 2010-02-03 14:19:49|
|Subject: Re: [HACKERS] Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1
ubuntu karmic slow createdb)|