Feedback-ID: i76984098:Fastmail
Message-ID: <1ad9842a-f3ec-456e-9251-0663c085e919@aklaver.com>
Date: Thu, 9 Jan 2025 09:05:14 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: recovery error while running any statement
To: yudhi s <learnerdatabase99@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
References: <CAEzWdqeNp1HRJt7SkQxANB60CMhrGuJsRKtEpu-Ghb_nXUvgoQ@mail.gmail.com>
 <86acb9be-a695-4902-b612-e2fb15339982@aklaver.com>
 <CAEzWdqcXB956YV_DjENVPtGyi3n-cUpNYkG57g4ZnZrUF2yecQ@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAEzWdqcXB956YV_DjENVPtGyi3n-cUpNYkG57g4ZnZrUF2yecQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/1ad9842a-f3ec-456e-9251-0663c085e919%40aklaver.com>
Precedence: bulk

On 1/9/25 09:01, yudhi s wrote:
> 
> On Thu, Jan 9, 2025 at 10:21 PM Adrian Klaver <adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.com>> wrote:
> 
>     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 <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.
> 
> 
> 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?

Since you have provided essentially zero information about your setup 
there is no real way to answer the above.

-- 
Adrian Klaver
adrian.klaver@aklaver.com