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 1tVviX-00Cj3k-By for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 16:49:09 +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 1tVviW-004Sdt-1o for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 16:49:07 +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 1tVviV-004SdS-NC for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 16:49:07 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVviS-000lQL-1f for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 16:49:07 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-29f9e76802aso1068026fac.1 for ; Thu, 09 Jan 2025 08:49:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736441343; x=1737046143; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=i8JcDHrShA7g+6U4MUIrqr3pB/X4rGmFOQh3muGmAB4=; b=Og+H80XINDzn8YZugQG1GUGrOgQKLIY0Hp9/fdglOvPnaI3noqYQ/97aTalCUzk/iS 8kce7aaOAHdkm+ysQn0ADMl6TImMpQRusYkQlWI+MOu2ANAV7m58SPUIFxcXFn2qaHQg y1KRbcQHZMtEUutrtzn9BbxMl1t3EvKHFL9epOoxJL4a+r6M5cWM+9EYzw0IfW5CR+aG qesduTbvlS9+J7ksZBuklLJ/rifgZnWYXzgwvvrmrLYh26BGInivsWtyjYkP9XY8MHkI YcDOw/2G5Rz912GAQqogeqv2ejKKbKwwq/oFNvZrkO6v/tL102xxkpP2KC8yC+iYNjA5 clFA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736441343; x=1737046143; h=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=i8JcDHrShA7g+6U4MUIrqr3pB/X4rGmFOQh3muGmAB4=; b=Kxulr6hsU6/tfN9JlFQXqd/SWEVhKUdSJXkXFbnbMJgLfVN171qXuJEYiXCjPd1rSs 1PfKbmQH7xrinmFxKcRrg+RTDGLFeFKUgZXUAHa+d0KVDzWP1dFbJN4A0YnUYv2Qg8y3 hlDjrpUbA08A9jnleJFpMaZD1TSSdwqIrhYdduhxVQecbepEDqVRqTbqYvz34DmzmstZ aB4g1hn282CdBqwePmPJrQ3LaX/G+5u9Q8Pcbrg2b1qPqk2SN0oaCenAJiw2/vJzRYHD /RVSuxTEWHV9iY4nyagg7YK/DDshanmThXdiMz3q5LEKTcMdokbeO1b8pMLFQJxxkGK7 hn4Q== X-Gm-Message-State: AOJu0Yyc35ohOiyu73eC8r305G7/XS2jDd7Blfqb7gaePPcUBjN5ZTlN QRvZtrBJj1Lv/DCyzWeMpSnzYWyvdS8ygiqHEaDD4g0FdPdk/TF7MoAKmzMrOutBysKpBPk0Vup DVY/1k9VV3lf0oZvoRJiOO/bu9DXIvg== X-Gm-Gg: ASbGnct4mZ4hk+w5SjB7CWnycL9NkxQR8oZuPfpfoSxrarlepCKpKQ2vCtVQtAG3BuH o+EbQ9u17PNc4qOee4SNBjnaMAw8O0kGKmR56DJLcMTNa+8jYycU/gyZJSCTWLbK1nkbVBcou X-Google-Smtp-Source: AGHT+IE9q2E0upWdPLjIykYs7gIk8R0Yl4Sq7Sb/Fh4QTVcPS8cx/5ayMVdZag4Y7jXeEtRNIoar9iza2pnoidiUqvc= X-Received: by 2002:a05:6870:9c8d:b0:29e:7629:1466 with SMTP id 586e51a60fabf-2aacdbc936amr2276586fac.7.1736441343016; Thu, 09 Jan 2025 08:49:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Thu, 9 Jan 2025 11:48:52 -0500 X-Gm-Features: AbW1kvaEBS0GEyVSQS7FsWhvrZw-rX5qfKnuhB2dx9R0_vNzPkVjiNC66s5q-8A Message-ID: Subject: Re: recovery error while running any statement To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006c8963062b48c163" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006c8963062b48c163 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 9, 2025 at 11:42=E2=80=AFAM yudhi s wrote: > Hello Experts, > It's postgres aurora version 16. While running the ALTER command on any > 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 "*c= annot > set transaction read-write mode during recovery*". > > Want to understand , what is the cause of this error and how to fix this? > The cause of the error is that the instance is in recovery mode, just like the error message says. Is your system a cluster? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000006c8963062b48c163 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Jan 9, 2025 at 11:42=E2=80=AFAM y= udhi s <learnerdatabase99= @gmail.com> wrote:
Hel= lo Experts,
It's postgres aurora version 16. While=C2=A0 running th= e ALTER command on any object we see an error "Only RowExclusiveLoc= k 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 transac= tion read-write" and it erroring out with "cannot set tran= saction read-write mode during recovery".

Want to understand=C2=A0, what is the cause of this error and how to fix t= his?

The cause of the error is = that the instance is in recovery mode, just like the error message says.

Is your system a cluster?

= --
Death to <Redacted>, and butter= sauce.
Don't boil me, I'm still alive.
<Redact= ed> lobster!
--0000000000006c8963062b48c163--