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 1tVvlJ-00CjRp-Ru for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 16:52:02 +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 1tVvlJ-004WG8-CP for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 16:52:01 +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 1tVvlI-004WFb-G3 for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 16:52:00 +0000 Received: from fout-a6-smtp.messagingengine.com ([103.168.172.149]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tVvlE-000lRg-1D for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 16:51:59 +0000 Received: from phl-compute-08.internal (phl-compute-08.phl.internal [10.202.2.48]) by mailfout.phl.internal (Postfix) with ESMTP id 97D6013801BC; Thu, 9 Jan 2025 11:51:54 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-08.internal (MEProxy); Thu, 09 Jan 2025 11:51:54 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1736441514; x=1736527914; bh=Iazh4W7yGgxhl2G/Nudd9xxJidFfVIsbH0Gq4QZGOtI=; b= qJAYUdqkxNjtZ+ks1CoGgwrAQHM8XPVKKq9w8d5qMQrF/+ajoql/0JkCA9EkdWNW Hyj05RgjKXoqf16BZXjvNg6r9hodG8jRLBCUI/e47IRL3QBn2c47pmxj78CVjHGU yZ1mnWmD0I0lXj8LRodCUN1RmqTH5owq8kR2XG6A8vKmkDPAIFH3LuGqVqMoriyT zVc5E3x1R9WXev+EBbbZXylq75ANhJL5ctg7UfDuUufV4s0U1cPCYYLfLHvHclUR LzVcksGZ9gyUXta16rSvjPeF+/s/WqXfjz8GsADGKJezvRQDulPTJxTU8tahIQpV X2WtdZCeeE9Q7J3Cjw26xQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1736441514; x=1736527914; bh=I azh4W7yGgxhl2G/Nudd9xxJidFfVIsbH0Gq4QZGOtI=; b=fYzqWucnYFYXIPhiD wioVYXrvn6kfkC13Wm9eINliryyQIfnPZP0sUha6DRUZc6SvhvC8hvseoom2pfTo TmVAPtTkmLukr6yHWYUlwv5KxxNazJF7cBXd3DB/C194fqXbfuEFOpu2YC2ImuBG 3xm5qI0J2t6Xp/X79yLUaGHCqG8SpZqpwcpmOCL9v7H3p/uZloJafPKu5GCvmx87 be4HUJL0y92Jp6hIP/R8pbqcAl5RcnkYU3iTbp5YIzd04ms4VxhbywYoRLYMnVGN CyVzfIvYEhtJQNciIALuJOiQ31u4yjAZcWZFDy+PVer5iIjAfy9T+fyS/wh8rKBs 0qJ+Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrudegiedgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfg fuvfhfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghr uceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrth htvghrnhepgfdvuddvkeeugfelteehuefgvdeludetudekfefgtdfgveduieffkeduledt heeinecuffhomhgrihhnpegrmhgriihonhdrtghomhenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhl rghvvghrrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhuthdprh gtphhtthhopehlvggrrhhnvghruggrthgrsggrshgvleelsehgmhgrihhlrdgtohhmpdhr tghpthhtohepphhgshhqlhdqghgvnhgvrhgrlheslhhishhtshdrphhoshhtghhrvghsqh hlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 Jan 2025 11:51:53 -0500 (EST) Message-ID: <86acb9be-a695-4902-b612-e2fb15339982@aklaver.com> Date: Thu, 9 Jan 2025 08:51:53 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: recovery error while running any statement To: yudhi s , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/9/25 08:42, 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 "/cannot set transaction read-write mode during recovery/". > > Want to understand , what is the cause of this error and how to fix this? Per: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html Aurora Postgres is not the community edition, you should probably take this up with AWS support. > > Regards > Yudhi -- Adrian Klaver adrian.klaver@aklaver.com