public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: recovery error while running any statement
Date: Thu, 9 Jan 2025 12:10:51 -0500
Message-ID: <CANzqJaDyE5cCcemxtj3xMBa49GCHpqP2Ewm2mC_NySikcfEGdQ@mail.gmail.com> (raw)
In-Reply-To: <CAEzWdqcXB956YV_DjENVPtGyi3n-cUpNYkG57g4ZnZrUF2yecQ@mail.gmail.com>
References: <CAEzWdqeNp1HRJt7SkQxANB60CMhrGuJsRKtEpu-Ghb_nXUvgoQ@mail.gmail.com>
<[email protected]>
<CAEzWdqcXB956YV_DjENVPtGyi3n-cUpNYkG57g4ZnZrUF2yecQ@mail.gmail.com>
On Thu, Jan 9, 2025 at 12:01 PM yudhi s <[email protected]> wrote:
>
> On Thu, Jan 9, 2025 at 10:21 PM Adrian Klaver <[email protected]>
> 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
>>
>> 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?
>
Are you *positive* that you're connected to the *primary* node? Because
this is exactly the kind of error you'll see when connected to the
*secondary* node.
Or maybe, for some reason, AWS failed you over to the secondary node,
making it now the primary node, while what you think is the primary node is
really the secondary node.
That's how "real" Postgresql acts, at least. Not how AWS RDS Postgresql
acts (it's all hidden behind a virtual IP that you always connect to), but
I don't know anything about Aurora.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: recovery error while running any statement
In-Reply-To: <CANzqJaDyE5cCcemxtj3xMBa49GCHpqP2Ewm2mC_NySikcfEGdQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox