| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2021-08-12 release announcement draft |
| Date: | 2021-08-11 18:29:24 |
| Message-ID: | CAH2-WzntmH6kP10KHc7VtWT9OtLWdK8mph0d6Y+nP=-LHePK7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 11, 2021 at 11:23 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> How about:
>
> * `pg_upgrade` now carries forward the old installation's `oldestXID`
> value, which can improve things from a performance standpoint by no
> longer forcing an anti-wraparound `VACUUM`.
I don't think that framing this as a performance thing really makes
sense. It certainly helps performance to not do something that's
totally unnecessary, and only ever happened because of a bug in the
implementation. But to me the point is that we're not doing these
weird wholly unnecessary antiwraparound VACUUMs on upgrade now.
Running pg_upgrade no longer affects when or how we VACUUM, which is
exactly what you'd expect all along.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2021-08-11 18:42:38 | Re: 2021-08-12 release announcement draft |
| Previous Message | Jonathan S. Katz | 2021-08-11 18:23:51 | Re: 2021-08-12 release announcement draft |