On Wed, Jun 15, 2022 at 4:13 AM Mauro Farracha wrote:
> The scenario:
> - Out of nowhere (during the weekend), without database activity load or
> batches running, with previous nightly run of vacuum freeze, in the middle of
> the day, with xids and mxids below 20M we are seeing autovacuum being
Frankly speaking, Aurora PostgreSQL's behaviour is quite unpredictable.
In our case, the autovacuum was not even getting triggered in spite of
crossing the autovacuum_freeze_max_age. Finally, the database went down
abruptly, which resolved the issue.
Thanks,
Ninad
On Wed, Jun 15, 2022 at 7:57 PM
On Wed, 2022-06-15 at 12:13 +0100, Mauro Farracha wrote:
> Have recently upgraded from PG10 to PG13.5 and would like to understand the
> reason why we
> are seeing triggered autovacuum to prevent the wraparound while all the
> metrics are still
> far off from the multixact/freeze max ages defined
Hello guys,
Have recently upgraded from PG10 to PG13.5 and would like to understand the
reason why we are seeing triggered autovacuum to prevent the wraparound
while all the metrics are still far off from the multixact/freeze max ages
defined. And inclusive there was one time where it was triggere
