Re: Re: performance bottlenecks on lock transactionid

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: 王若楠 <wrn(at)hljdx(dot)net>, pgsql-performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: performance bottlenecks on lock transactionid
Date: 2019-08-14 10:25:58
Message-ID: 60f01304bbdefa9d091145b77a117df2d7b5a5ca.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

王若楠 wrote:
> I want to find a way to reduce the lock waiting and improve the
> performance.

You either have to make the transactions shorter, or you let the
different clients modify different rows, so that they don't lock each
other.

That concurrent writers on the same data lock each other is
unavoidable, and all database management systems I know do it the same
way.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Adrian Klaver 2019-08-14 14:13:43 Re: ORA-24345: A Truncation or null fetch error occurred -ora2pg
Previous Message Daulat Ram 2019-08-14 09:39:43 RE: ORA-24345: A Truncation or null fetch error occurred -ora2pg