public inbox for [email protected]  

help / color / mirror / Atom feed

Re: recovery error while running any statement
2+ messages / 2 participants
[nested] [flat]

* Re: recovery error while running any statement
@ 2025-01-09 17:01 yudhi s <[email protected]>
  2025-01-09 17:05 ` Re: recovery error while running any statement Adrian Klaver <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: yudhi s @ 2025-01-09 17:01 UTC (permalink / raw)
  To: Adrian Klaver <[email protected]>; +Cc: pgsql-general <[email protected]>

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?


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: recovery error while running any statement
  2025-01-09 17:01 Re: recovery error while running any statement yudhi s <[email protected]>
@ 2025-01-09 17:05 ` Adrian Klaver <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Adrian Klaver @ 2025-01-09 17:05 UTC (permalink / raw)
  To: yudhi s <[email protected]>; +Cc: pgsql-general <[email protected]>

On 1/9/25 09:01, yudhi s wrote:
> 
> On Thu, Jan 9, 2025 at 10:21 PM Adrian Klaver <[email protected] 
> <mailto:[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 <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
[email protected]







^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2025-01-09 17:05 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-01-09 17:01 Re: recovery error while running any statement yudhi s <[email protected]>
2025-01-09 17:05 ` Adrian Klaver <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox