Re: oldest xmin is far in the past :: BUT xmin is not available in system

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: bhargav kamineni <kbn98406(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: oldest xmin is far in the past :: BUT xmin is not available in system
Date: 2022-04-19 15:48:29
Message-ID: CAH2-Wz=vb+ZULB=2XQuzZpm6SCF3M_jN1382=1vKURF2vi=7tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Apr 18, 2022 at 11:37 PM bhargav kamineni <kbn98406(at)gmail(dot)com> wrote:
> executing the vacuum on the entire cluster is also giving the same HINTS and WARNING's

You're using Aurora, not PostgreSQL. Perhaps this is actually a bug,
but there is no way for anybody here to know.

--
Peter Geoghegan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2022-04-19 17:11:27 Re: PostgreSQL 10.20 crashes / Antivirus
Previous Message Tom Lane 2022-04-19 15:38:49 Re: oldest xmin is far in the past :: BUT xmin is not available in system