From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Yuri Niyazov <yuri@academia.edu>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Figuring out the correct age of datfrozenxid
Date: Fri, 26 Jul 2019 13:57:22 -0400
Message-ID: <20190726175722.GA7885@alvherre.pgsql> (raw)
In-Reply-To: <CACuBw0hbStKjfKBEPE+weS=jp00iOxLkNCJ9XmXehwsanCg5Wg@mail.gmail.com>
On 2019-Jul-25, Yuri Niyazov wrote:
> all the tables have a very reasonable age, but the database itself still
> has an age approaching two billion. So, what do we do now?
I think vacuuming any table will update the database age. For instance,
try creating an empty table and do "vacuum freeze" on it.
> Were we wrong to truncate and drop this unneeded table without letting
> a vacuum on it finish?
That seems an appropriate measure to have taken You just need to have
the system figure out that it's gone.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: pgsql-admin@postgresql.org
Cc: alvherre@2ndquadrant.com, yuri@academia.edu, pgsql-admin@lists.postgresql.org
Subject: Re: Figuring out the correct age of datfrozenxid
In-Reply-To: <20190726175722.GA7885@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox