From: Laurenz Albe <laurenz.albe@cybertec.at>
To: 王若楠 <wrn@hljdx.net>
To: pgsql-performance <pgsql-performance@lists.postgresql.org>
Subject: Re: Re: performance bottlenecks on lock transactionid
Date: Wed, 14 Aug 2019 12:25:58 +0200
Message-ID: <60f01304bbdefa9d091145b77a117df2d7b5a5ca.camel@cybertec.at> (raw)
In-Reply-To: <tencent_25DF4C35A54D4A33B5206E53BF6D468BB208@qq.com>
References: <tencent_25DF4C35A54D4A33B5206E53BF6D468BB208@qq.com>
王若楠 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
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: laurenz.albe@cybertec.at, wrn@hljdx.net, pgsql-performance@lists.postgresql.org
Subject: Re: Re: performance bottlenecks on lock transactionid
In-Reply-To: <60f01304bbdefa9d091145b77a117df2d7b5a5ca.camel@cybertec.at>
* 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