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 1tVvud-00Ckqu-OD for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 17:01:40 +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 1tVvuc-004ina-Uv for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 17:01:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tVvuc-004ihU-JM for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 17:01:38 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVvua-000jtE-0m for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 17:01:37 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-29fae583cc8so562500fac.1 for ; Thu, 09 Jan 2025 09:01:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736442096; x=1737046896; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=PAjLv3Xtuhcj8/1Xbo4VJOmnSsVKeVFVly7FiS0unrI=; b=JkTyH1TTvX7BOmAt6vGazz+5OPN5S4ZVtzmBbxYG2TYJg+2bM5VjYYJJDHFqsvJAWY hVa+RiYXXtQ4nLMGJQ9crR2Ec0dPFYykmCNoRrdq04q1Jd4adrTgsBVVvYPPrKjhKhG3 0aljVdJIbTkJeyO6eCQqDJt+7XOwA6yXGYJX7Yvd1Ge/phS4bHg/vTbX876nDSYtn4uC PwVqd/2d/dfnWV3ImyvserpF6o1hoFgVG2THmsOJcrJN6wDUrAggegh6ZaEFORq9VKr5 D9P4gP0N6b1koiH1QVxCQksmv6SqwAp3RlSYPJlKDf2ndkgJ2abBiAqL0aXn1VKknZGw 9rmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736442096; x=1737046896; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=PAjLv3Xtuhcj8/1Xbo4VJOmnSsVKeVFVly7FiS0unrI=; b=bAxfCnta7KJvxnjFmqEaYMMrYy/eqxfuXFtq2OJwI0LMPGxyxKCrzgN7GwddBc/R/F bKfFmUaqtQC+6Mfwkzss2j4PB4DBD/EM5DbGsjTGdF+LSG4Y6Xws35b1U+H0XOspwIpC pHxo2ZbP5AxwgPrU433pEnVp9A9kFmYOOc3zAA4LhmqHpita61qISv1BtEEeHVX/UrJB Xxjr5I4ctFa4lhGajiHnBq6pvsyyufwAurYnV0VaCjzSyVihAAbtjAgirTTSKk59lWzs 5Pl6YxjP6X8xa2Fdx9Z2wNTydibQrLwaDY8OQWQIaxIwFeG6ppMXZXk1sumlgrKQSQ/9 gmcw== X-Gm-Message-State: AOJu0Ywy+VDEWI3OxsaIjAmLky2OVnUv7n3eWeiRupFX9ppPIgFXlh+6 Ln1w7Wkv4Rf3FfmmjtFLQcn/66xMj7ypvy1mOltTUn3WnEBLTwZkABmQxmL09OizryS4T2R7XM5 GScxeqEUyJ9VGeo9CRi0C1zzDVmF61g== X-Gm-Gg: ASbGncuvzRruChnKQ5kDfjP4BjrY/XZwU2UvRb5hgcshUDVE65QISfawkwgkLvfbdpu CTCrM8UKcDF0VpTUuAyg/x/9PykO8fBwd4Pa3EhX7JqsvF8bMbI9kwMuWOvhY+vyO4RsRExX8 X-Google-Smtp-Source: AGHT+IFIgWj7nfst2mMsCE4hs/Zk4yqGFgybCs94bG38LNLTkmcItbxNT90qiy0YCMNtkjANNI2RAep0e4UO5iPbrLI= X-Received: by 2002:a05:6871:ea14:b0:2a7:8c73:be33 with SMTP id 586e51a60fabf-2ad8087abc9mr1555062fac.16.1736442094262; Thu, 09 Jan 2025 09:01:34 -0800 (PST) MIME-Version: 1.0 References: <86acb9be-a695-4902-b612-e2fb15339982@aklaver.com> In-Reply-To: <86acb9be-a695-4902-b612-e2fb15339982@aklaver.com> From: yudhi s Date: Thu, 9 Jan 2025 22:31:20 +0530 X-Gm-Features: AbW1kvbxPE9Lq6sC8QKdhsRMA74QI2ziDdyPvE6SeqfsBH98NBFuRbjbs8fgn2c Message-ID: Subject: Re: recovery error while running any statement To: Adrian Klaver Cc: pgsql-general Content-Type: multipart/alternative; boundary="00000000000033a18f062b48eeec" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000033a18f062b48eeec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 9, 2025 at 10:21=E2=80=AFPM Adrian Klaver wrote: > On 1/9/25 08:42, yudhi s wrote: > > Hello Experts, > > It's postgres aurora version 16. While running the ALTER command on an= y > > object we see an error "/Only RowExclusiveLock or less can be acquired > > on database objects during recovery/". If I run any DML it gives an > > error stating '/cannot execute UPDATE in a read-only transaction/' , > > then I tried setting "/set transaction read-write/" and it erroring out > > with "/cannot set transaction read-write mode during recovery/". > > > > Want to understand , what is the cause of this error and how to fix thi= s? > > Per: > > > https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Auror= aPostgreSQL.html > > Aurora Postgres is not the community edition, you should probably take > this up with AWS support. > > > Sure will raise a ticket. I was trying to understand though , if it's possible in postgres to have these sudden "recovery errors" possible because of some long running DML/DDL killed unexpectedly using the "pg_terminate/pg_cancel" command? And if this error appears in community postgres and if it stays for a long time what we used to do? --00000000000033a18f062b48eeec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Jan 9, 2025= at 10:21=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 1/9/25 08:42, yudhi s wrote:
> Hello Experts,
> It's postgres aurora version 16. While=C2=A0 running the ALTER com= mand on any
> object we see an error "/Only RowExclusiveLock or less can be acq= uired
> on database objects during recovery/". If I run any DML it gives = an
> error stating '/cannot execute UPDATE in a read-only transaction/&= #39; ,
> then I tried setting "/set transaction read-write/" and it e= rroring out
> with "/cannot set transaction read-write mode during recovery/&qu= ot;.
>
> Want to understand=C2=A0, what is the cause of this error and how to f= ix this?

Per:

https://doc= s.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.h= tml

Aurora Postgres is not the community edition, you should probably take
this up with AWS support.


Sure will raise a ticket. I was trying to underst= and=C2=A0though=C2=A0, if it's possible in postgres to have these sudde= n "recovery errors" possible because of some long running DML/DDL= killed unexpectedly using the "pg_terminate/pg_cancel" command? = And if this error appears in community postgres and if it stays for a long = time what we=C2=A0used to do?=C2=A0
=C2=A0
--00000000000033a18f062b48eeec--