Re: A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a explosive replication lag. Oh my.

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ian Axelrod <ian(dot)axelrod(at)sentilink(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: A thousand pg_commit_ts truncate attempts per second, two restarting autovacuum processes, and a explosive replication lag. Oh my.
Date: 2025-05-06 11:28:18
Message-ID: 3e709006f5bdf123bb0f5882099e299cbd48efb5.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2025-05-05 at 23:52 -0500, Ian Axelrod wrote:
> This issue occurred on an AWS RDS Aurora PostgreSQL installation.

Aurora is different from PostgreSQL. In particular, the query cancellation
error you are showing does not occur in the PostgreSQL code base. So unless
somebody who knows Aurora internals happens to read your question, you won't
get a good answer.

You could check if your I/O quota are exceeded...

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-05-06 11:47:37 Re: Add an option to skip loading missing publication to avoid logical replication failure
Previous Message Zhijie Hou (Fujitsu) 2025-05-06 11:22:27 RE: Fix slot synchronization with two_phase decoding enabled