Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qjDVX-009rWl-UZ for pgsql-general@arkaria.postgresql.org; Thu, 21 Sep 2023 06:49:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qjDVW-0099zl-44 for pgsql-general@arkaria.postgresql.org; Thu, 21 Sep 2023 06:49:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qjDVV-0099zO-NL for pgsql-general@lists.postgresql.org; Thu, 21 Sep 2023 06:49:49 +0000 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qjDVS-006TEP-Uk for pgsql-general@lists.postgresql.org; Thu, 21 Sep 2023 06:49:49 +0000 Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-53348be3fe1so122987a12.2 for ; Wed, 20 Sep 2023 23:49:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1695278986; x=1695883786; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=Ld6E0/kUPNz01tG0rH7rkZA4Um8ku5kP2EVHll7zLSM=; b=lGObz3gZP4Ra2MDDK0TDqaGlZb4bK966V/WVKcMBec/R0uPuAv+murXt/lvhVJx3gb wH3DIEiG7Vv2KDK5pIa3PXyhpztvsbDMpGxBeYTIWXh2WKiKfHgpA2r49FipQdjPJnwc EiVdJm7wb186EyP3EGGnR0xh6D+Vy0ZoctDsBRql6tqBlV+u/KCU7N9hEWqkteeoL4dQ MeuskLXv49LTF+h2sWKxyUceJt+mg3OaN9Yf+1W3LT0N83o1vnabCXtFRWBgs2lH3/eW mAgLA4xedkwk5pvVgkTc1cAJVoqDm7fWE8Kv41M5r2QHVRMf/cq1Jrp4k5pIDRbJRDYu DA5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695278986; x=1695883786; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Ld6E0/kUPNz01tG0rH7rkZA4Um8ku5kP2EVHll7zLSM=; b=hMddLzBXDjSnRCLrn6IkyH3HRrzGhust8HX9de6bwE4rd0nPRYsrrqQy4LGGzqyJFV UzFTBHuNqMUpIjqTKMqnKfqoWepza9BW62FD94svBp2HTF/DreE/pLwazcKjE0wd2OVf MIsk4ql5ylUIjx7tefojJQ6c424TOXZ/EBKHytmq2JEEE9xV0TNE//GdE/TfRNQQCNRv 9MoXBf9JkXm2VsqRHjg69QrON79lIqdR0ZclnJcpEQg/8/OD9J2P7MI5wFCYoamPl75Y 7mGpbx/5jcUcx9FPKs6QS9jfaim3DYJdXXxzTnrGso491gY6h1w/10WMb6/Ys3U8L+Gl QfQA== X-Gm-Message-State: AOJu0YzLmoUfaKkTwfCIhUGOl9YCkOD58tA/9Twz3/xNLQQKshDqJ0fw fG67oAD2TqwCI3/HWKzgpqo2bcQpPLVKILaLVKA= X-Google-Smtp-Source: AGHT+IHvgGElIf78M2gYdiN68z4arNEuu1Xks78ZJWg1jCkt2RFe+ZkpFx9elB0sjsTDb4tnwTnjNg== X-Received: by 2002:a05:6402:746:b0:532:e4d3:df83 with SMTP id p6-20020a056402074600b00532e4d3df83mr3830785edy.4.1695278986021; Wed, 20 Sep 2023 23:49:46 -0700 (PDT) Received: from localhost.localdomain (62-46-255-1.adsl.highway.telekom.at. [62.46.255.1]) by smtp.gmail.com with ESMTPSA id z25-20020aa7c659000000b00530ba0fd672sm382253edr.75.2023.09.20.23.49.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Sep 2023 23:49:45 -0700 (PDT) Message-ID: Subject: Re: Database selection From: Laurenz Albe To: veem v Cc: pgsql-general Date: Thu, 21 Sep 2023 08:49:45 +0200 In-Reply-To: References: <52e7f6118cb91faa10e2b44d2af5bd69d4502238.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 exa= ct > 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 alterna= tives. 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 main= taining > the transactions?=20 > 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