From: Laurenz Albe <laurenz.albe@cybertec.at>
To: veem v <veema0000@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Database selection
Date: Thu, 21 Sep 2023 08:49:45 +0200
Message-ID: <a02fc2f1245740102a45ca7f68e40162b88635c8.camel@cybertec.at> (raw)
In-Reply-To: <CAB+=1TUUUTseZH+fTUi5yf0RdDQ8rU3_kyTkP7=ACOGGu=7SAg@mail.gmail.com>
References: <CAB+=1TUNYzAxCskmx3Hko4+7eeXzZ0cXCzCkB9dYJ19kaD=eDA@mail.gmail.com>
<52e7f6118cb91faa10e2b44d2af5bd69d4502238.camel@cybertec.at>
<CAB+=1TUUUTseZH+fTUi5yf0RdDQ8rU3_kyTkP7=ACOGGu=7SAg@mail.gmail.com>
On Thu, 2023-09-21 at 02:41 +0530, veem v wrote:
> However, One of the things regarding the transaction management, which I see in
> most postgres blogs is 'mvcc'(multiversion concurrency control) being an issue
> at times in a heavy concurrent system, in postgres as its maintaining exact
> copies of all the old versions of the rows(if someone still reading those) and
> at times cleaning these(vacuuming) becomes a pain.
If your workload consists of updating rows over and over at high frequency, that
is particularly hard for PostgreSQL, and you might want to consider alternatives.
There are ways to mitigate the impact (HOT update), but that requires some design
and planning effort.
> Does AWS aurora postgres depend on the same vacuuming technology for maintaining
> the transactions?
> Does Aurora Mysql opt for a similar strategy for transaction management? or any
> different/better ones?
Nobody except Amazon can tell. It is closed source.
Yours,
Laurenz Albe
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: laurenz.albe@cybertec.at, veema0000@gmail.com
Subject: Re: Database selection
In-Reply-To: <a02fc2f1245740102a45ca7f68e40162b88635c8.camel@cybertec.at>
References: <CAB+=1TUNYzAxCskmx3Hko4+7eeXzZ0cXCzCkB9dYJ19kaD=eDA@mail.gmail.com> <52e7f6118cb91faa10e2b44d2af5bd69d4502238.camel@cybertec.at> <CAB+=1TUUUTseZH+fTUi5yf0RdDQ8rU3_kyTkP7=ACOGGu=7SAg@mail.gmail.com> <a02fc2f1245740102a45ca7f68e40162b88635c8.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