| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Yuri Niyazov <yuri(at)academia(dot)edu> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Figuring out the correct age of datfrozenxid |
| Date: | 2019-07-26 17:57:22 |
| Message-ID: | 20190726175722.GA7885@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mariel Cherkassky | 2019-07-28 15:16:43 | upgrading cluster with 2 nodes to new major version |
| Previous Message | Yuri Niyazov | 2019-07-26 05:12:57 | Figuring out the correct age of datfrozenxid |